generated from ansible-collections/collection_template
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postgresql_idx only takes into account idxname (not schema) #692
Comments
rlaager
added a commit
to rlaager/community.postgresql
that referenced
this issue
May 8, 2024
When chekcing to see if an index exists, the schema name needs to be taken into account. That is, the same name can exist in multiple schemas. Closes ansible-collections#692
rlaager
added a commit
to rlaager/community.postgresql
that referenced
this issue
May 8, 2024
When chekcing to see if an index exists, the schema name needs to be taken into account. That is, the same name can exist in multiple schemas. Fixes ansible-collections#692
rlaager
added a commit
to rlaager/community.postgresql
that referenced
this issue
May 8, 2024
When checking to see if an index exists, the schema name needs to be taken into account. That is, the same name can exist in multiple schemas. Fixes ansible-collections#692
rlaager
added a commit
to rlaager/community.postgresql
that referenced
this issue
May 8, 2024
When checking to see if an index exists, the schema name needs to be taken into account. That is, the same name can exist in multiple schemas. Fixes ansible-collections#692
Andersson007
pushed a commit
that referenced
this issue
May 10, 2024
When checking to see if an index exists, the schema name needs to be taken into account. That is, the same name can exist in multiple schemas. Fixes #692
hunleyd
pushed a commit
that referenced
this issue
May 10, 2024
When checking to see if an index exists, the schema name needs to be taken into account. That is, the same name can exist in multiple schemas. Fixes #692 (cherry picked from commit 09fec84) Co-authored-by: Richard Laager <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
postgresql_idx only takes into account the idxname, not the schema, when deciding whether the index already exists.
ISSUE TYPE
COMPONENT NAME
community.postgresql.postgresql_idx
ANSIBLE VERSION```paste below
ansible [core 2.13.13]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/srv/ansible/modules']
ansible python module location = /srv/ansible/.venv/lib/python3.8/site-packages/ansible
ansible collection location = /srv/ansible/.venv/share/ansible/collections:/home/rlaager/.ansible/collections:/usr/share/ansible/collections:/usr/local/share/ansible/collections
executable location = /srv/ansible/.venv/bin/ansible
python version = 3.8.10 (default, Nov 22 2023, 10:22:35) [GCC 9.4.0]
jinja version = 3.1.3
libyaml = False
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 20.04 with Ansible installed in virtualenv
STEPS TO REPRODUCE
EXPECTED RESULTS
On the first run, I would expect it to create one index per schema.
ACTUAL RESULTS
On the first run, it creates the index for the first schema and then the subsequent iterations of the loop are "ok".
The text was updated successfully, but these errors were encountered: