Horton
Menu

RE: [PATCH] Support automatic sequence replication

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

View thread
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'Dilip Kumar' <dilipbalaut@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>
Cc: Ajin Cherian <itsajin@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-23T05:44:46Z
Lists: pgsql-hackers 
Dear Dilip,

> Thanks for clarifying the use case, and I agree this is a valid use
> case, although I am not completely sure how exactly we are achieving
> that? I mean sequence sync workers need to fetch the list of all
> published sequences to identify whether they are in sync with the
> local sequence state or not?  Or somehow we can avoid that?  If not
> what we would save, updating the local states of the sequences if they
> are already in sync?

IIUC, the sequencesync worker first lists all sequences on the subscriber, then
gets their states on the publisher side. Then the worker updates the state only
when the sequence between instances is different.

Does it make sense for you?

Best regards,
Hayato Kuroda
FUJITSU LIMITED

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.