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.

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

pg_failover_slots extension with CNPG #41

Open
MathCharton opened this issue Apr 18, 2024 · 1 comment
Open

pg_failover_slots extension with CNPG #41

MathCharton opened this issue Apr 18, 2024 · 1 comment

Comments

@MathCharton
Copy link

Hello,
I'm trying to use this extension with CNPG and i have no problem with basic configuration, however, i have a few questions.
This is my context and configuration:

  • I have a primary and one replica

  • I'm using a CDC tool (debezium) that's why i need this extension to ensure that i will not lose data after failover / switchover

  • About configuration:
    hot_standby_feedback: on
    pg_failover_slots.synchronize_slot_names: debezium
    I dont use primary_slot_name because i noticed that with CNPG, this value is never empty (can you confirm it ?)

  • Questions:

  1. I would like to use pg_failover_slots.standby_slot_names parameter to ensure that i will not lose data, so if I've understood correctly, I need to set the value of my replica physical's replication_slot ! (for example the slot used for streaming_replication ?)
    ex: pg_failover_slots.standby_slot_names = cnpg-test-2 (in case of cnpg-test-1 is primary db)

  2. So in case of failover/switchover , cnpg-test-1 become replica and what about pg_failover_slots.standby_slot_names value ? Should i manually upgrade the value to pg_failover_slots.standby_slot_names = cnpg-test-1 ?

  3. Is there a way to retrieve this physical's replication_slot name (replica pod) into the manifest declaration ?

thanks

@acsezen
Copy link

acsezen commented Oct 21, 2024

Hello,

Have very similar scenario. Is there any answer for it from the team ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants