| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | "amit(dot)kapila16(at)gmail(dot)com" <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: sequencesync worker race with REFRESH SEQUENCES |
| Date: | 2026-07-24 12:38:35 |
| Message-ID: | CALDaNm0pKs=vWvzNgSTJ6HJpVtWLiAcW2LA8rBvX91MD0i0fPA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 24 Jul 2026 at 10:49, Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Hmm, but tablesync workers, which can connect to the publisher by itself are not
> terminated by the function. IIUC, tablesync workers can read the subscription
> catalog and recognize the catalog. I feel we should follow that approach.
Yes it is better to keep sequence synchronization worker also similar.
The attached v2 version has the changes to call
maybe_reread_subscription and identify if the subscription is
disabled.
Regards,
Vignesh
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Fix-issues-reported-by-claude.patch | application/octet-stream | 9.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2026-07-24 12:56:12 | Re: Changing shared_buffers without restart |
| Previous Message | Zsolt Parragi | 2026-07-24 12:04:33 | Re: [PATCH] Use ssup_datum_*_cmp for int2, oid, and oid8 sort support |