PostgreSQL community pinboard

[dagwieers]

This has all moved to community.postgres collection repository.

[dagwieers]

cc @fessmage @Andersson007 @astorath @tcraxs @kostiantyn-nemchenko @antoinell @zikalino @frittentheke @jbscalia @lichensky @m4ci3k2 @Glandos @chamini2 @sebasmannem @nerzhul @tdtrask @pilou- @strk @archf @Dorn- @indreek @gshivani
cc @andytom @gothicx @jbscalia @kustodian @vfoucault @tedder @amenonsen @herrewig @michael-dev2rights @acasademont @wrouesnel @joshmoore @willthames @woqer @veger @aleksandr-vin @jirutka @simonalpha
cc @matburt

[dagwieers]

If you want to actively lead or are interested to be part of this Working Group, add your name to the Wiki page ! If we have a large enough group, we can start our own PostgreSQL Working Group.

I started labeling all the PostgreSQL related issues and PRs so we can more easily track them:

• https://github.com/ansible/ansible/pulls?q=is:pr+is:open+label:postgresql (20 open PRs)
• https://github.com/ansible/ansible/issues?q=is:issue+is:open+label:postgresql (22 open issues)

PS If you no longer want to receive any messages from this pinboard, feel free to unsubscribe from this issue ticket.

[Andersson007]

@dagwieers , thank you for this invatation! If nobody is reasonably against I'd like to actively lead this group. I hope everything works out.

[dagwieers]

@Andersson007 Great and thanks ! We do allow more than one leading a Working Group, as long as it helps moving forward and engages the community as a whole I support every new idea. There are no strict rules we try to learn as we go with this new concept of technology-related communities.

There's a lot of open PRs to review and open issues to verify, so everyone is welcome to make the upcoming Ansible v2.8 release the best one for PostgreSQL support. We have about one more month to get our act together!

[mattclay]

@dagwieers We do have test infrastructure for PostgreSQL. We have the postgresql integration tests which spin up their own instance for testing, which are run by CI.

[dagwieers]

@mattclay I stand corrected. However the current integration tests are lacking any tests for postgresql_ext, postgresql_idx, postgresql_lang and postgresql_schema modules. So I will add this to the PostgreSQL Wiki.

[Andersson007]

Who can explain me a couple of questions about writing and execution of integration tests?

[dagwieers]

@Andersson007 Integration tests live in our tree in test/integration/targets/. I wrote some information about integration tests at: https://github.com/ansible/community/wiki/Reviewing#integration-tests

My integration tests typically look like this: https://github.com/ansible/ansible/blob/devel/test/integration/targets/mso_tenant/tasks/main.yml

Running an integration test is done using:

$ ansible-test integration --allow-unsupported <target-name>

You can add --docker for running tests in a container, read ansible-test integration --help for more information.

[Andersson007]

@dagwieers, thank you for this useful info! I hope it will be useful for all. This is convenient to use docker for this. I tried to run - nothing difficult.
I'm going to try to write tests for all of my new recent modules
and, if success, maybe for existing modules without tests.
Would be better if other contributors from working group help to add this tests for them too.

[antoinell]

Thanks Andrey for working on this. I also started fiddling with docker today. I did a 11.5 miles run today and my energy was spent there. I noticed all the useful comments you wrote on ansible/ansible#50568 <ansible/ansible#50568> and I hope to get started implementing this slowly. My current work does not use postgresql so I need to get to run postgresql in docker first to do some exploratory research such as finding which query gives the options of a tablespace in case one is working on an existing tablespace and the code needs to check whether the current options match the options requested by the user. Regards, Antoine

…

On Feb 2, 2019, at 2:14 PM, Andrey Klychkov ***@***.***> wrote: @dagwieers <https://github.com/dagwieers>, thank you for this useful info! I hope it will be useful for all. This is convenient to use docker for this. I tried to run - nothing difficult. I'm going to try to write tests for all of my new recent modules and, if success, maybe for existing modules without tests. Would be better if other contributors from working group help to add this tests for them too. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#435 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAckbGC5JoiIsv85Ofjttn8ELlIB6VRaks5vJeN7gaJpZM4acdcw>.

[Andersson007]

Any ideas what's going on on freebsd 11 ? ansible/ansible#51875

04:57 The full traceback is:
04:57 Traceback (most recent call last):
04:57   File "/tmp/ansible_postgresql_set_payload_PtOEQV/__main__.py", line 308, in main
04:57     db_connection = psycopg2.connect(**kw)
04:57   File "/usr/local/lib/python2.7/site-packages/psycopg2/__init__.py", line 130, in connect
04:57     conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
04:57 OperationalError: fe_sendauth: no password supplied
04:57 
04:57 
04:57 fatal: [testhost]: FAILED! => {
04:57     "changed": false, 
04:57     "invocation": {
04:57         "module_args": {
04:57             "db": null, 
04:57             "login_host": "", 
04:57             "login_password": "", 
04:57             "login_unix_socket": "", 
04:57             "login_user": "postgres", 
04:57             "name": "work_mem", 
04:57             "port": 5432, 
04:57             "reset": null, 
04:57             "session_role": null, 
04:57             "ssl_mode": "prefer", 
04:57             "ssl_rootcert": null, 
04:57             "value": "12MB"
04:57         }
04:57     }, 
04:57     "msg": "unable to connect to database: fe_sendauth: no password supplied\n"
04:57 }
04:57 ...ignoring
04:57 
04:57 TASK [postgresql : assert] *****************************************************
04:57 task path: /root/.ansible/test/tmp/postgresql-Cl4cwA-ÅÑŚÌβŁÈ/test/integration/targets/postgresql/tasks/postgresql_set.yml:26
04:57 fatal: [testhost]: FAILED! => {
04:57     "msg": "The conditional check 'set_wm.name == 'work_mem'' failed. The error was: error while evaluating conditional (set_wm.name == 'work_mem'): 'dict object' has no attribute 'name'"
04:57 }

Seems it relates with default authentication freebsd11 but why another tests passed this successfully...