MIME-Version: 1.0
References: <CAFPTHDZXX9WQ_X1ZfEvS248T+pKuk6SmCnXcvgPM059N1xPUfA@mail.gmail.com>
In-Reply-To: <CAFPTHDZXX9WQ_X1ZfEvS248T+pKuk6SmCnXcvgPM059N1xPUfA@mail.gmail.com>
From: Dilip Kumar <dilipbalaut@gmail.com>
Date: Fri, 20 Feb 2026 10:10:40 +0530
Message-ID: <CAFiTN-tFanrK2S=ALc++vmOnS07mumSLA91aaYejBHi7X8+rUg@mail.gmail.com>
Subject: Re: [PATCH] Support automatic sequence replication
To: Ajin Cherian <itsajin@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFiTN-tFanrK2S%3DALc%2B%2BvmOnS07mumSLA91aaYejBHi7X8%2BrUg%40mail.gmail.com>
Precedence: bulk

On Tue, Feb 3, 2026 at 9:18=E2=80=AFAM Ajin Cherian <itsajin@gmail.com> wro=
te:
>
> 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=E2=80=99d like to understand
how updating the value at specific intervals will improve the user
experience.

--=20
Regards,
Dilip Kumar
Google