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

From Tom Lane
Subject Re: pg_sequence_last_value() for unlogged sequences on standbys
Date
Msg-id 86044.1715108521@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_sequence_last_value() for unlogged sequences on standbys  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: pg_sequence_last_value() for unlogged sequences on standbys
List pgsql-hackers
Nathan Bossart <nathandbossart@gmail.com> writes:
> On Tue, May 07, 2024 at 01:44:16PM -0400, Tom Lane wrote:
>> +1 to include that, as it offers a defense if someone invokes this
>> function directly.  In HEAD we could then rip out the test in the
>> view.

> I apologize for belaboring this point, but I don't see how we would be
> comfortable removing that check unless we are okay with other sessions'
> temporary sequences appearing in the view, albeit with a NULL last_value.

Oh!  You're right, I'm wrong.  I was looking at the CASE filter, which
we could get rid of -- but the "WHERE NOT pg_is_other_temp_schema(N.oid)"
part has to stay.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: backend stuck in DataFileExtend
Next
From: "Tristan Partin"
Date:
Subject: Re: Use pgstat_kind_infos to read fixed shared stats structs