Skip to content
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.

Sign up for GitHub

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

docs-1149: add note to avoid create extension cmd #6340

Merged
merged 2 commits into from
Dec 19, 2024
Merged

docs-1149: add note to avoid create extension cmd #6340

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8eb0aeb
add note to avoid create extension cmd
piano35-edb Dec 10, 2024
ed5ba22
edit to should not
piano35-edb Dec 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions advocacy_docs/pg_extensions/pg_failover_slots/configuring.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@ navTitle: Configuring

You must add the extension to `shared_preload_libraries` on both the primary instance as well as any standby that's used for high availability (failover or switchover) purposes.

!!!Note
You should not run the `CREATE EXTENSION` command for PG Failover Slots.

## Prerequisite settings

The following settings are required:
Expand Down
2 changes: 1 addition & 1 deletion advocacy_docs/pg_extensions/pg_failover_slots/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ directoryDefaults:
PG Failover Slots (pg_failover_slots) is an extension released as open source software under the PostgreSQL License. If you have logical replication publications on Postgres databases that are also part of a streaming replication architecture,
PG Failover Slots avoids the need for you to reseed your logical replication tables when a new standby gets promoted to primary.

Since the replication slot used by logical replication is maintained only on the primary node, downstream subscribers don't receive any new changes from the newly promoted primary until the slot is created on the newly promoted primary. Picking up logical replication changes from the newly promoted standby is unsafe because THE following information will be lost:
Since the replication slot used by logical replication is maintained only on the primary node, downstream subscribers don't receive any new changes from the newly promoted primary until the slot is created on the newly promoted primary. Picking up logical replication changes from the newly promoted standby is unsafe because the following information will be lost:
- The data a subscriber confirmed receiving
- The log data that still needs to be retained for the subscriber

Expand Down
Loading