| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Replication slot is not able to sync up |
| Date: | 2025-06-17 06:30:58 |
| Message-ID: | CAA4eK1+MdzAT5BvAM=2Xbieig3Br07gOcrozLJAkm58mthGDHg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 16, 2025 at 9:27 AM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> Thanks Peter and Amit for feedback. I have updated the patch.
>
<para>
+ When slot-synchronization setup is done as recommended, and
+ slot-synchronization is performed the very first time either automatically
+ or by <link linkend="pg-sync-replication-slots">
+ <function>pg_sync_replication_slots</function></link>,
+ then for the synchronized slot to be created and persisted on the standby,
+ one condition must be met. The logical replication slot on the primary
+ must reach a state where the WALs and system catalog rows retained by
+ the slot are also present on the corresponding standby server. This is
+ needed to prevent any data loss and to allow logical replication
to continue
+
...
This whole paragraph sounds like a duplicate of its previous section,
and the line alignment in the first paragraph has some issues.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2025-06-17 06:48:07 | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
| Previous Message | Daniel Gustafsson | 2025-06-17 06:28:34 | Re: pg_upgrade fails with an error "object doesn't exist" |