Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values
Date
Msg-id 62710.75.177.135.163.1173748853.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Gregory Stark wrote:
> "Tom Lane" <tgl@sss.pgh.pa.us> writes:
>
>> petere@postgresql.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Inconsistent behavior on select * from void_function()?
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values