| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Joachim Wieland" <joe(at)mcknight(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| Date: | 2007-03-13 01:20:53 |
| Message-ID: | 62710.75.177.135.163.1173748853.squirrel@www.dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Gregory Stark wrote:
> "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
>> petere(at)postgresql(dot)org (Peter Eisentraut) writes:
>>> Make configuration parameters fall back to their default values when
>>> they
>>> are removed from the configuration file.
>>
>> It appears that this patch has broken custom GUC variables; at the very
>> least it's broken plperl.
>
> Huh, it occurs to me that I haven't seen any plperl regression tests fly
> by
> when I've been running regression tests myself. What do I have to do to
> test
> if plperl, plpython, etc work with the packed varlena patch?
>
cd src/pl; make installcheck
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-13 01:26:10 | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| Previous Message | Gregory Stark | 2007-03-13 01:13:15 | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-13 01:26:10 | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| Previous Message | Tom Lane | 2007-03-13 01:20:14 | Re: Inconsistent behavior on select * from void_function()? |