From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Merlin Moncure <mmoncure(at)gmail(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Subject: | Re: advisory locks and permissions |
Date: | 2006-09-22 15:10:09 |
Message-ID: | 29024.1158937809@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-09-22 15:10:17 | Re: 8.3 Development Cycle |
Previous Message | Bruno Wolff III | 2006-09-22 15:07:37 | Re: Fixed length data types issue |