Re: Logical Replication of sequences

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: shveta malik <shveta(dot)malik(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Euler Taveira <euler(at)eulerto(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Subject: Re: Logical Replication of sequences
Date: 2025-07-17 11:21:53
Message-ID: CALDaNm1K59nt2BZwGdyTyifabGrfSB=6=b+_Y89rL=hPsr_FGg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 16 Jul 2025 at 11:15, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Mon, Jul 14, 2025 at 10:03 AM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> >
> > On Fri, 11 Jul 2025 at 14:26, shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
> > >
> I have picked this up again for final review, started with 0001, I
> think mostly 0001 looks good to me, except few comments
>
> 1.
> + lsn = PageGetLSN(page);
> + last_value = seq->last_value;
> + log_cnt = seq->log_cnt;
> + is_called = seq->is_called;
> +
> + UnlockReleaseBuffer(buf);
> + sequence_close(seqrel, NoLock);
> +
> + /* Page LSN for the sequence */
> + values[0] = LSNGetDatum(lsn);
> +
> + /* The value most recently returned by nextval in the current session */
> + values[1] = Int64GetDatum(last_value);
> +
>
> I think we can avoid using extra variables like lsn, last_value etc
> instead we can directly copy into the value[$] as shown below.
>
> values[0] = LSNGetDatum(PageGetLSN(page));
> values[1] = Int64GetDatum(seq->last_value);
> ...
> UnlockReleaseBuffer(buf);
> sequence_close(seqrel, NoLock);

Modified

> 2.
> + <para>
> + Returns information about the sequence. <literal>page_lsn</literal> is
> + the page LSN of the sequence, <literal>last_value</literal> is the
> + current value of the sequence, <literal>log_cnt</literal> shows how
> + many fetches remain before a new WAL record must be written, and
> + <literal>is_called</literal> indicates whether the sequence has been
> + used.
>
> Shall we change 'is the page LSN of the sequence' to 'is the page LSN
> of the sequence relation'

Modified

> And I think this field doesn't seem to be very relevant for the user,
> although we are exposing it because we need it for internal use.
> Maybe at least the commit message of this patch should give some
> details on why we need to expose this field.

Updated commit message

The attached v20250717 version patch has the changes for the same.

Regards,
Vignesh

Attachment Content-Type Size
v20250717-0001-Introduce-pg_sequence_state-function-for-e.patch text/x-patch 7.6 KB
v20250717-0003-Reorganize-tablesync-Code-and-Introduce-sy.patch text/x-patch 23.0 KB
v20250717-0004-Introduce-REFRESH-PUBLICATION-SEQUENCES-fo.patch text/x-patch 43.1 KB
v20250717-0005-New-worker-for-sequence-synchronization-du.patch text/x-patch 73.4 KB
v20250717-0002-Introduce-ALL-SEQUENCES-support-for-Postgr.patch text/x-patch 104.8 KB
v20250717-0006-Documentation-for-sequence-synchronization.patch text/x-patch 33.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2025-07-17 11:24:15 Re: [V2] Adding new CRC32C implementation for IBM S390X
Previous Message shveta malik 2025-07-17 11:14:11 Re: Conflict detection for update_deleted in logical replication