From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: plpgsql GUC variable: custom or built-in? |
Date: | 2010-04-20 01:08:41 |
Message-ID: | x2y603c8f071004191808u86ffd9c4v2b08b1a1d3a81bfd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 12, 2009 at 6:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-04-20 01:23:17 | Re: shared_buffers documentation |
Previous Message | Robert Haas | 2010-04-20 00:55:59 | Re: Streaming replication and a disk full in primary |