Re: [HACKERS] pageinspect option to forgo buffer locking?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] pageinspect option to forgo buffer locking?
Date: 2018-02-21 19:37:22
Message-ID: CAH2-Wz=kCzi4E7kNjWkd9_+iQu90mLHX-j6ubAbwZWDopZP=9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 9, 2017 at 2:21 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> 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!

I hope that you follow up on this soon.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Brian Cloutier 2018-02-21 19:41:31 Re: Add PGDLLIMPORT to enable_hashagg
Previous Message Rady, Doug 2018-02-21 19:11:15 Re: [PATCH] pgbench - refactor some connection finish/null into common function