merge #7
Open
merge #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Avoid problem when jinja2 treats value 'on' as True. In result in pg config will be value True
Remove extra single quotes from the log_line_prefix option.
…uster deployment (#464)
…uired) (#761) Previously, the role for creating extensions was executed before the restart, which could result in errors, example: failed: [10.129.50.35] (item={'ext': 'pg_cron', 'db': 'postgres', 'schema': 'pg_catalog'}) => {"ansible_loop_var": "item", "changed": false, "item": {"db": "postgres", "ext": "pg_cron", "schema": "pg_catalog"}, "msg": "Management of PostgreSQL extension failed: pg_cron can only be loaded via shared_preload_libraries\nHINT: Add pg_cron to the shared_preload_libraries configuration variable in ********ql.conf.\n"} Now, extensions will be created after the restart. Note: If the `pending_restart: true` variable is set, the cluster will be restarted if required (e.g., when changing `shared_preload_libraries`).
This update modifies the stanza creation process for pgbackrest to run on all nodes only if repo1-type is posix. For other types (e.g., S3), the stanza creation is limited to the primary node, addressing errors caused by running stanza creation on multiple hosts in non-posix setups.
With the release of pgvectorscale v0.4.0, the minimum supported version of PostgreSQL 13
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Run stanza-delete on pgbackrest repo-host (if defined), or on the first postgres node if not.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Co-authored-by: Vitaliy Kukharik <[email protected]>
Removed the password requirement.
Check if the user pgbouncer exists before creating the 'user_search' function.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.