pgbouncer: Сreate the 'user_search' function in pgbouncer_auth_dbname only #568
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to optimize adding the user_search function to {{pgbouncer_auth_dbname }} only and only once, if the given function already exists, the playbook will not perform the function creation step, when pgbouncer_auth_user is 'true'.
When pgbouncer_auth_user is 'false' a block will be used to create a userlist file.
When pgbouncer_auth_user is 'true', the playbook will use the block to create the user_search function in {{pgbouncer_auth_dbname }} only on the master server.
When restarting the playbook, when the user_search function is already exists in {{pgbouncer_auth_dbname }}, there will only be a stage of checking for the existence of this function, there will be no repeat stage to add the function.