Re: sequencesync worker race with REFRESH SEQUENCES

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: sequencesync worker race with REFRESH SEQUENCES
Date: 2026-07-20 06:41:31
Message-ID: CALDaNm0Yt4ZxOjZ=acZr9YRRDt1qAfMzW9Vv_A4yJ0r62H7N_w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 15 Jul 2026 at 17:23, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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 Content-Type Size
v4_PG19-0001-Ignore-default_transaction_read_only-in-sequence-.patch application/octet-stream 3.7 KB
v4-0001-Allow-logical-replication-workers-to-ignore-defau.patch application/octet-stream 4.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-07-20 06:47:41 Re: TDE: Benchmarking WAL encryption approaches
Previous Message wenhui qiu 2026-07-20 06:23:59 Re: WAL compression setting after PostgreSQL LZ4 default change