Re: [HACKERS] pageinspect option to forgo buffer locking? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] pageinspect option to forgo buffer locking?
Date
Msg-id 20171109222145.iwf46ebcgmw3qib3@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] pageinspect option to forgo buffer locking?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] pageinspect option to forgo buffer locking?  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On 2017-11-09 17:14:11 -0500, Tom Lane wrote:
> If we do this, I'd suggest exposing it as a separate SQL function
> get_raw_page_unlocked() rather than as an option to get_raw_page().
> 
> The reasoning is that if we ever allow these functions to be controlled
> via GRANT instead of hardwired superuser checks (cf nearby debate about
> lo_import/lo_export), one might reasonably consider the unlocked form as
> more risky than the locked form, and hence not wish to have to give out
> privileges to both at once.

Good idea!


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] pageinspect option to forgo buffer locking?
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [PATCH] A hook for session start