RE: [PATCH] Support automatic sequence replication - Mailing list pgsql-hackers

From Zhijie Hou (Fujitsu)
Subject RE: [PATCH] Support automatic sequence replication
Date
Msg-id TY4PR01MB16907CE099565A5F1A311B2599440A@TY4PR01MB16907.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: [PATCH] Support automatic sequence replication  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses Re: [PATCH] Support automatic sequence replication
List pgsql-hackers
On Friday, March 13, 2026 7:36 PM Kuroda, Hayato/黒田 隼人 <kuroda.hayato@fujitsu.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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Report bytes and transactions actually sent downtream
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] libpq: Fix incorrect message type in getBackendKeyData() comment