| From: | GF <phabriz(at)gmail(dot)com> |
|---|---|
| To: | Ramakrishna m <ram(dot)pgdb(at)gmail(dot)com> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Justin <zzzzz(dot)graf(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, ravisql09(at)gmail(dot)com |
| Subject: | Re: Logical Replication Delay |
| Date: | 2024-09-29 12:26:42 |
| Message-ID: | CAFePLY0q=tcuLzYjQdwncQS2ERZrzyFna27hex3vBYwWxFHe_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Ram,
29 set 2024, 12:29 Ramakrishna m <ram(dot)pgdb(at)gmail(dot)com>:
*We are planning to set up logical replication from a standby to another
> server. When the primary goes down, there is no issue as the standby
> becomes the primary and the logical slots are already present. However,
> when the standby goes down, these slots are not copied to the third node or
> the primary by Patroni. Is there an option available to handle this
> scenario? *
>
You could take a look at the pg_failover_slots extension (
https://www.enterprisedb.com/docs/pg_extensions/pg_failover_slots/) it is
aimed exactly at cloning the slot information to a standby.
Best,
giovanni
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Koen De Groote | 2024-09-29 14:48:54 | Basebackup fails without useful error message |
| Previous Message | Ramakrishna m | 2024-09-29 10:28:46 | Re: Logical Replication Delay |