Re: plpgsql GUC variable: custom or built-in?
От | Robert Haas |
---|---|
Тема | Re: plpgsql GUC variable: custom or built-in? |
Дата | |
Msg-id | x2y603c8f071004191808u86ffd9c4v2b08b1a1d3a81bfd@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: plpgsql GUC variable: custom or built-in? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: plpgsql GUC variable: custom or built-in?
|
Список | pgsql-hackers |
On Thu, Nov 12, 2009 at 6:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: >> With all this fallout, I think it would be cleaner to step back and make >> it a regular GUC variable, not custom. Pretending that plpgsql is >> somehow not an integral part of the system is not completely true >> anyway. Yes, we're playing favorites in the PL camp here, but so what? > > True, but on the other hand, if plpgsql needs this to work nicely, then > $YOURPL probably needs it too. This thread is still on the open items list, as: Improve behavior of SUSET GUC variables added by loadable modules? Is there something that needs to be done here? If so, what is it? ...Robert
В списке pgsql-hackers по дате отправления: