RE: [PATCH] Support automatic sequence replication

From: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: [PATCH] Support automatic sequence replication
Date: 2026-03-16 06:58:52
Message-ID: TY4PR01MB16907CE099565A5F1A311B2599440A@TY4PR01MB16907.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Friday, March 13, 2026 7:36 PM Kuroda, Hayato/黒田 隼人 <kuroda(dot)hayato(at)fujitsu(dot)com> wrote:

> Thanks for updating the patch. Comments for v12-0002.

Thanks for the comments.

After some off-list discussion with Amit, we agreed that further analysis is
needed, which means rescheduling this feature for the next release.

The main issue requiring analysis is how to reduce the impact of invalidations
that can occur once the sequence synchronization worker begins modifying
pg_subscription_rel regularly. The current patch updates pg_subscription_rel
only every 30 seconds, which seems acceptable for an initial version. However,
there are other potential approaches worth exploring, such as: 1) adding a
subscription option to let users control the update frequency, or 2) updating
the catalog only after modifying a specific number of sequences.

It would also be worthwhile to examine other modules for similar issues and
their solutions. For example, autoanalyze and autovacuum also modify the catalog
regularly. We should investigate whether they face the same invalidation
challenges and how those challenges are addressed.

Overall, we will continue working on this to improve the patch set, but will
schedule it for PG20.

Best Regards,
Hou zj

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-03-16 07:00:36 Re: [PATCH] libpq: Fix incorrect message type in getBackendKeyData() comment
Previous Message Michael Paquier 2026-03-16 06:50:28 Re: Report bytes and transactions actually sent downtream