-
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: consider schema name when checking #693
postgresql_idx: consider schema name when checking #693
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the fix! could you please add a changelog fragment under the bugfix: key?
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
85fb83c
to
e8b980f
Compare
Done. I'm not sure how verbose you want me to be. I can drop the additional sentences if you prefer shorter. Also, I wasn't able to find documentation on things like line length, so let me know if I need to rewrap the code (the exec_sql statement) or the changelog fragment. |
@rlaager hi, welcome to the project and thanks for the contribution! |
Backport to stable-2: 💚 backport PR created✅ Backport PR branch: Backported as #694 🤖 @patchback |
Merged! |
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]>
SUMMARY
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
ISSUE TYPE
COMPONENT NAME
community.general.postgresql_idx