Horton
Menu

Re: [PATCH] Support automatic sequence replication

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: shveta malik <shveta.malik@gmail.com>
Cc: Ajin Cherian <itsajin@gmail.com>, Ashutosh Sharma <ashu.coek88@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-18T07:41:48Z
Lists: pgsql-hackers 
On Wed, Feb 18, 2026 at 12:36 PM shveta malik <shveta.malik@gmail.com> wrote:
>
> I tested a few scenarios on the latest patch. Sequence sync worker did
> not stop in below scenarios:
>
> 1) When the subscription was disabled.
> 2) When the only publication for sequences was dropped from
> subscription ( ALTER SUBSCRIPTION sub1 DROP PUBLICATION pub_seq;)
> 3) When all sequences were dropped on sub.
>
> Application worker stops in scenario 1, seq-sync worker should also
> stop. See maybe_reread_subscription().
>
> We need to decide the behavior of the seq-sync worker for 2 and 3.
>

Shouldn't we try to map (2) and (3) to what we do for table publication?

-- 
With Regards,
Amit Kapila.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Don't include wait_event.h in pgstat.h

  2. Don't include proc.h in shm_mq.h

  3. Fix unsafe RTE_GROUP removal in simplify_EXISTS_query

  4. Add sequence synchronization for logical replication.