Magnus Hagander wrote:
On Mon, Mar 12, 2007 at 08:20:53PM -0500, Andrew Dunstan wrote:
Gregory Stark wrote:
"Tom Lane" <[EMAIL PROTECTED]> writes:
[EMAIL PROTECTED] (Peter Eisentraut) writes:
Make configuration parameters fall back to their default values when
they
ar
On Mon, Mar 12, 2007 at 08:20:53PM -0500, Andrew Dunstan wrote:
> Gregory Stark wrote:
> > "Tom Lane" <[EMAIL PROTECTED]> writes:
> >
> >> [EMAIL PROTECTED] (Peter Eisentraut) writes:
> >>> Make configuration parameters fall back to their default values when
> >>> they
> >>> are removed from the co
Gregory Stark <[EMAIL PROTECTED]> writes:
> 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 to $TOP/src/pl, run "make install
Gregory Stark wrote:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>
>> [EMAIL PROTECTED] (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 varia
"Tom Lane" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (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 br
[EMAIL PROTECTED] (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.
regards, to
