Add support for extensions loading and creation.#399
Conversation
|
Can one of the admins verify this patch? |
2 similar comments
|
Can one of the admins verify this patch? |
|
Can one of the admins verify this patch? |
|
Why did you remove file |
|
[test] |
|
I removed it because this is used in the test, and would interfer with them. However, you are right, removing the file make the example incorrect, as the whole README is no longer correct. A better solution would be to either remove the cp line and keep the example as is, or duplicate the test, so we can test the old way, and the new one. I will send a updated PR once the tests are finished. |
|
I just got done deploying Postgres13 from these changes as a back end to my Discourse instance. They worked for me and allowed me to automate the processes I have been struggling to automate cleanly for a while now. We are going to either need to maintain these changes or have them upstreamed for a Discourse Template we plan to go live somewhere close to next week. I built it from the instructions in the first README.md. The following might be useful if it was updated to reflect the steps to build on Fedora, e.g. from: to something like: |
82b0b9b to
570df13
Compare
|
Ok so I tried my best to test the old way and the new way. And for the failure on testing-farm.io, I am unsure what to do, I rebased hoping this would somehow fix the problem. |
570df13 to
031f77f
Compare
|
[test] |
031f77f to
7b3bb19
Compare
|
Last push should fix the error: (which is the only error I see on https://ci.centos.org/job/SCLo-container-postgresql-rh-fedora/292/timestamps/?time=HH:mm:ss&timeZone=GMT+2&appendLog&locale=en_GB ) |
7b3bb19 to
4f25398
Compare
|
So I regenerated like the other PR. |
4f25398 to
756d7f9
Compare
|
I rebased again (conflicts). |
|
@mscherer Please rebase it against master including common submodule. |
15bd4a8 to
f7205f4
Compare
|
Rebased [test] |
|
Let's test after generated sources. [test] |
|
Strange behaviour. There is an error in -----------------------------------------------
Running test run_pgaudit_test (starting at 2023-10-03 10:26:59+00:00) ...
-----------------------------------------------
c644c8223c59eb64a932a2d1cd2e13e9f3bee4a1c7fd79ec69e1df6e37a788c0
Created container c644c8223c59eb64a932a2d1cd2e13e9f3bee4a1c7fd79ec69e1df6e37a788c0
test/run: line 340: $1: unbound variable
Tests finished with EXIT=1
Tests are passing: ==============================================
Tests were run for image quay.io/sclorg/postgresql-15-c9s:1
==============================================
Test cases results:
[PASSED] for 'postgresql-container_tests' run_container_creation_tests (00:00:19)
[PASSED] for 'postgresql-container_tests' run_general_tests (00:00:39)
[PASSED] for 'postgresql-container_tests' run_change_password_test (00:00:07)
[PASSED] for 'postgresql-container_tests' run_replication_test (00:00:06)
[PASSED] for 'postgresql-container_tests' run_doc_test (00:00:00)
[PASSED] for 'postgresql-container_tests' run_s2i_test (00:00:14)
[PASSED] for 'postgresql-container_tests' run_test_cfg_hook (00:00:08)
[PASSED] for 'postgresql-container_tests' run_s2i_bake_data_test (00:00:12)
[PASSED] for 'postgresql-container_tests' run_s2i_enable_ssl_test (00:00:08)
[PASSED] for 'postgresql-container_tests' run_upgrade_test (00:00:00)
[PASSED] for 'postgresql-container_tests' run_migration_test (00:00:23) |
phracek
left a comment
There was a problem hiding this comment.
I hit some issues, that needs to be fixed.
|
@mscherer Please address my comments, if they are relevant. |
@phracek Hi, have you encountered this problem repeatedly? I will create a issue from this so we will not forget it. |
Using POSTGRESQL_LIBRARIES and POSTGRESQL_EXTENSIONS allow users to enable extensions (some bundled in the container) without having to do anything but adding 2 variables.
|
[test] |
|
Tests passed; upgrade test is a known issue. Otherwise LGTM |
Initially command `test was missing`, but after it was added test failed and crashed in a way that no more tests were run. This behavior is known issue tracked here in issue sclorg#537 Problem is that `DOCKER_EXTRA_ARGS` variable is set already which it shouldn't be, so the `test` command returns 0, so no `cp` happens and we get the crash. Variable is empty, but apparently do exist as `test -v DOCKER_EXTRA_ARGS` is `TRUE`. Introduced by PR sclorg#399
Initially command `test was missing`, but after it was added test failed and crashed in a way that no more tests were run. This behavior is known issue tracked here in issue #537 Problem is that `DOCKER_EXTRA_ARGS` variable is set already which it shouldn't be, so the `test` command returns 0, so no `cp` happens and we get the crash. Variable is empty, but apparently do exist as `test -v DOCKER_EXTRA_ARGS` is `TRUE`. Introduced by PR #399
Using POSTGRESQL_LIBRARIES and POSTGRESQL_EXTENSIONS allow
users to enable extensions (some bundled in the container) without
having to do anything but adding 2 variables.