Re: advisory locks and permissions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: advisory locks and permissions
Date
Msg-id 29024.1158937809@sss.pgh.pa.us
Whole thread Raw
In response to Re: advisory locks and permissions  (Stephen Frost <sfrost@snowman.net>)
Responses Re: advisory locks and permissions  ("Merlin Moncure" <mmoncure@gmail.com>)
Re: advisory locks and permissions  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> An admin who is concerned about this can revoke public access on the
>> functions for himself ... but should that be the default out-of-the-box
>> configuration?  I feel more comfortable with saying "you have to turn
>> on this potentially-dangerous feature" than with saying you have to turn
>> it off.

> I agree with having it turned off by default, at least in 8.2.

Do we have a consensus to do this for 8.2?  Or are we going to leave it
as is?  Those are the only two realistic short-term options ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: Fixed length data types issue
Next
From: "Joshua D. Drake"
Date:
Subject: Re: 8.3 Development Cycle