public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dilip Kumar <[email protected]>
To: Ajin Cherian <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: [PATCH] Support automatic sequence replication
Date: Fri, 20 Feb 2026 10:10:40 +0530
Message-ID: <CAFiTN-tFanrK2S=ALc++vmOnS07mumSLA91aaYejBHi7X8+rUg@mail.gmail.com> (raw)
In-Reply-To: <CAFPTHDZXX9WQ_X1ZfEvS248T+pKuk6SmCnXcvgPM059N1xPUfA@mail.gmail.com>
References: <CAFPTHDZXX9WQ_X1ZfEvS248T+pKuk6SmCnXcvgPM059N1xPUfA@mail.gmail.com>

On Tue, Feb 3, 2026 at 9:18 AM Ajin Cherian <[email protected]> wrote:
>
> Hello hackers,
>
> I'd like to propose an improvement to the sequence replication feature
> that was committed in [1].
>
> The current implementation synchronizes sequences during initial
> subscription setup, but the sequence sync worker exits after this
> initial sync. This means that as sequences advance on the publisher,
> they drift from the subscriber values over time. Users must manually
> run ALTER SUBSCRIPTION ... REFRESH SEQUENCES to resynchronize, which
> requires monitoring and intervention.

Thanks, Ajin, for the proposal. I am trying to think: what is the use
case for automatically updating the sequence values? IIUC, the only
use case for the sequence sync worker was when using logical
replication for an upgrade; after the upgrade, you should have
up-to-date values for the sequences. By adding an automatic update,
are you targeting any new use case?

If we are still targeting the same use case, I’d like to understand
how updating the value at specific intervals will improve the user
experience.

-- 
Regards,
Dilip Kumar
Google

view thread (5+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [PATCH] Support automatic sequence replication
  In-Reply-To: <CAFiTN-tFanrK2S=ALc++vmOnS07mumSLA91aaYejBHi7X8+rUg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox