Re: sequencesync worker race with REFRESH SEQUENCES - Mailing list pgsql-hackers

From vignesh C
Subject Re: sequencesync worker race with REFRESH SEQUENCES
Date
Msg-id CALDaNm0Yt4ZxOjZ=acZr9YRRDt1qAfMzW9Vv_A4yJ0r62H7N_w@mail.gmail.com
Whole thread
In response to Re: sequencesync worker race with REFRESH SEQUENCES  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Wed, 15 Jul 2026 at 17:23, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> So, I prefer the GUC approach and we are
> already overriding it for session_replication_role and search_path
> GUC's. The one minor difference could be that for PG19, we set it only
> for sequencesync worker and in HEAD for all workers.

Here is a patch to handle the same. v4-0001 patch has the changes to
set default_transaction_read_only guc in InitializeLogRepWorker which
is common to logical replication workers in master branch and v4_PG19
patch has the changes to set default_transaction_read_only guc in
SequenceSyncWorkerMain which is only for sequence sync worker.

Regards,
Vignesh

Attachment

pgsql-hackers by date:

Previous
From: wenhui qiu
Date:
Subject: Re: WAL compression setting after PostgreSQL LZ4 default change
Next
From: Zsolt Parragi
Date:
Subject: Re: TDE: Benchmarking WAL encryption approaches