Re: pg_sequence_last_value() for unlogged sequences on standbys - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_sequence_last_value() for unlogged sequences on standbys
Date
Msg-id ZjYDvGuHaf_Cx5Pb@paquier.xyz
Whole thread Raw
In response to Re: pg_sequence_last_value() for unlogged sequences on standbys  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_sequence_last_value() for unlogged sequences on standbys
List pgsql-hackers
On Fri, May 03, 2024 at 05:22:06PM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> IIUC this would cause other sessions' temporary sequences to appear in the
>> view.  Is that desirable?
>
> I assume Michael meant to move the test into the C code, not drop
> it entirely --- I agree we don't want that.

Yup.  I meant to remove it from the script and keep only something in
the C code to avoid the duplication, but you're right that the temp
sequences would create more noise than now.

> Moving it has some attraction, but pg_is_other_temp_schema() is also
> used in a lot of information_schema views, so we couldn't get rid of
> it without a lot of further hacking.  Not sure we want to relocate
> that filter responsibility in just one view.

Okay.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg17 issues with not-null contraints
Next
From: Michael Paquier
Date:
Subject: Re: pg_sequence_last_value() for unlogged sequences on standbys