From: | Petr Jelinek <pjmodos(at)pjmodos(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GRANT ON ALL IN schema |
Date: | 2009-08-21 22:02:46 |
Message-ID: | 4A8F1986.3030506@pjmodos.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane napsal(a):
>> That's really ugly. It'll cause catalog bloat with every execution.
>> I think it would be acceptable to have a new column in pg_language that
>> pointed to an anonymous block execute function. Languages that do not
>> define this function cannot use this new feature.
>>
>
> +1. The other way would also (presumably) mean invoking the language's
> validate procedure, which might well be redundant and in any case would
> probably not have exactly the error-reporting behavior one would want.
> I think it's better if the language knows it's dealing with an anonymous
> block. You could even imagine the language relaxing its rules a bit,
> for instance not requiring an outer BEGIN/END in plpgsql.
>
Alright I can do it this way.
However there is one question about implementing it in plpgsql.
Currently, the compiler reads info directly from heap tuple, so I either
have to write separate compiler for inline functions or change the
existing one to accept the required info as parameters and "fabricate"
some of it when compiling inline function. I am unsure which one is the
preferred way.
--
Regards
Petr Jelinek (PJMODOS)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-21 22:06:25 | Re: SIGUSR1 pingpong between master na autovacum launcher causes crash |
Previous Message | Alvaro Herrera | 2009-08-21 21:48:11 | Re: SIGUSR1 pingpong between master na autovacum launcher causes crash |