Cédric Villemain

the PR is supposed to address this issue.

https://github.com/ansible-collections/community.postgresql/pull/166 is covering all PostgreSQL versions on ubuntu-2004

So you need 2 tasks (get info, act if required), why adding complexity here ? To be clear: -1 from me. I fail to see a real use-case. Examples ?

Hi @zyitingftnt do you have updates for this issue or can it be closed (assuming this bug is not relevant for this collection) ? Tks

@zyitingftnt tks for the feedback, indeed the ansible answer on the issues are of interest and outline that some PostgreSQL modules need attention. From a security point of view, I...

while `postgresql-common` is very useful (provide pg_lscluster, pg_virtualenv and so on) it is often installed only in debian family distributions. It can be installed on RH but it usually is...

ok, we agree on the mapping between existing tools and a module. The needs for better cluster management might be of interest, I'm sure the point will raise as soon...

> The test runs look really strange. It seems that sanity tests for one ansible-core version are run with multiple Python versions? That's something that should not happen. There should...

> Also I don't think `--coverage` should be supplied when running sanity tests. Managed by upstream action. @webknjaz comments ? > Another comment: it is necessary that the `echo` commands...

> For smaller repos, there's no need to do that either. Simply don't give ansible-test a (target) Python version, and it will automatically run unit tests for all Python versions...