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 ZjYEKqGuMt-gkVak@paquier.xyz
Whole thread Raw
In response to Re: pg_sequence_last_value() for unlogged sequences on standbys  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Fri, May 03, 2024 at 03:49:08PM -0500, Nathan Bossart wrote:
> On Wed, May 01, 2024 at 12:39:53PM +0900, Michael Paquier wrote:
>> By the way, shouldn't we also change the function to return NULL for a
>> failed permission check?  It would be possible to remove the
>> has_sequence_privilege() as well, thanks to that, and a duplication
>> between the code and the function view.  I've been looking around a
>> bit, noticing one use of this function in check_pgactivity (nagios
>> agent), and its query also has a has_sequence_privilege() so returning
>> NULL would simplify its definition in the long-run.  I'd suspect other
>> monitoring queries to do something similar to bypass permission
>> errors.
>
> I'm okay with that, but it would be v18 material that I'd track separately
> from the back-patchable fix proposed in this thread.

Of course.  I mean only the permission check simplification for HEAD.
My apologies if my words were unclear.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_sequence_last_value() for unlogged sequences on standbys
Next
From: Michael Paquier
Date:
Subject: Re: Weird test mixup