Re: GRANT ON ALL IN schema - Mailing list pgsql-hackers

From Robert Haas
Subject Re: GRANT ON ALL IN schema
Date
Msg-id 603c8f070908100909m69b876cdt1723f2fbd2462a40@mail.gmail.com
Whole thread Raw
In response to Re: GRANT ON ALL IN schema  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: GRANT ON ALL IN schema  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Mon, Aug 10, 2009 at 11:36 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> One fairly simple way would use a new SQL verb (say, DO) like this:
>
>> DO $$ something in plfoo $$ LANGUAGE plfoo;
>
> Yeah, this has been suggested before.  I can't see anything very wrong
> with it.
>
>> We could even default the langauge to plpgsql, for which you would then
>> just need:
>
>> DO $$ something in plpgsql $$;
>
> Add a GUC variable to set the default language, perhaps?
>
>> But to make it really nice you'd have to move away from pl programs as
>> strings. That would be a lot more work, and you really wouldn't want to
>> make it work with more than one PL for the sake of everyone's sanity.
>
> That would be an awful lot of messiness to save four keystrokes...

I think it would be awfully handy to integrate some of the features of
PL/pgsql into core SQL - especially variables, and also things like IF
and FOR...  but I'm not expecting it to happen any time soon, or maybe
ever.

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Ship documentation without intermediate tarballs Documentation
Next
From: Tom Lane
Date:
Subject: Re: machine-readable explain output v4