Bruce Momjian <[EMAIL PROTECTED]> writes:
> 7 . 3 O P E NI T E M S
>
> Loading 7.2 pg_dumps
> functions no longer public executable
> languages no longer public usable
Although it's reasonably easy to fix no-privileges problems for
functions after you l
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > 7 . 3 O P E NI T E M S
> >
> > Loading 7.2 pg_dumps
> > functions no longer public executable
> > languages no longer public usable
>
>
> Although it's reasonably easy to fix no-privileges prob
Tom Lane writes:
> I am thinking that the better course might be to have newly created
> languages default to USAGE PUBLIC, at least for a release or two.
That seems reasonable. Since everyone is supposed to use createlang,
that's the effective default anyway.
--
Peter Eisentraut [EMAIL PRO
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> I am thinking that the better course might be to have newly created
>> languages default to USAGE PUBLIC, at least for a release or two.
> That seems reasonable. Since everyone is supposed to use createlang,
> that's the effectiv
Hello!
On Mon, 23 Sep 2002, Tom Lane wrote:
> I am thinking that the better course might be to have newly created
> languages default to USAGE PUBLIC, at least for a release or two.
>
> We might also consider letting newly created functions default to
> EXECUTE PUBLIC. I think this is less esse
Tom Lane writes:
> How do you feel about allowing functions to default to EXECUTE PUBLIC?
Less excited, but if it gets us to the point of no known problems during
upgrade we might as well do it.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> How do you feel about allowing functions to default to EXECUTE PUBLIC?
> Less excited, but if it gets us to the point of no known problems during
> upgrade we might as well do it.
Okay, I've changed the defaults for both language
