Re: Logical Replication of sequences - Mailing list pgsql-hackers

From vignesh C
Subject Re: Logical Replication of sequences
Date
Msg-id CALDaNm0WcdSCoNPiE-5ek4J2dMJ5o111GPTzKCYj9G5i=ONYtQ@mail.gmail.com
Whole thread Raw
In response to Re: Logical Replication of sequences  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Logical Replication of sequences
List pgsql-hackers
On Wed, 5 Nov 2025 at 13:58, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Mon, Nov 3, 2025 at 8:46 PM vignesh C <vignesh21@gmail.com> wrote:
> >
> > The attached v20251103 patch has the changes for the same.
> >
>
> I have pushed the 0001 after making minor adjustments in tests and at
> a few other places. Kindly rebase and send the remaining patches.

I noticed a buildfarm failure on prion at [1].
The test failed on prion because it runs with the following additional
configuration:
log_error_verbosity = verbose

Due to this setting, the logs include an extra LOCATION line between
the WARNING and ERROR messages, which was not expected by the test:
2025-11-05 11:35:21.090 UTC [1357163:3] WARNING:  55000: mismatched or
renamed sequence on subscriber ("public.regress_s4")
2025-11-05 11:35:21.090 UTC [1357163:4] LOCATION:
report_sequence_errors, sequencesync.c:185
2025-11-05 11:35:21.090 UTC [1357163:5] ERROR:  55000: logical
replication sequence synchronization failed for subscription
"regress_seq_sub"

I'm working on a fix for this issue.

[1] - https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2025-11-05%2010%3A30%3A15

Regards,
Vignesh



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: mxid and mxoff wraparound issues in pg_upgrade
Next
From: Amit Kapila
Date:
Subject: Re: Logical Replication of sequences