Re: pg_get_sequence_data Shows Non-NULL last_value for Freshly Created Sequence

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_get_sequence_data Shows Non-NULL last_value for Freshly Created Sequence
Date: 2025-08-20 17:01:52
Message-ID: 1181763.1755709312@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> This function returns the values in the sequence tuple, primarily for
> pg_dump (see commit bd15b7d). IIUC your patch would break pg_dump on v18
> and newer versions.

The proposed patch includes a change to pg_dump that I suppose is
meant to compensate. But I'm not 100% sure that it does so correctly.
Anyway, given that it's supposed to provide low-level inspection of
the sequence tuple, I think that it's best not to be too cute.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-08-20 17:02:57 Re: Changing the state of data checksums in a running cluster
Previous Message Jeff Davis 2025-08-20 17:00:49 Re: Organize working memory under per-PlanState context