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

From Magnus Hagander
Subject Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values
Date
Msg-id 20070313084443.GC22636@svr2.hagander.net
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Mon, Mar 12, 2007 at 08:20:53PM -0500, Andrew Dunstan wrote:
> 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

Is there any particular reason why we don't run these as part of a
general "make check"?

//Magnus


pgsql-hackers by date:

Previous
From: "Sean Utt"
Date:
Subject: Re: My honours project - databases using dynamically attached entity-properties
Next
From: Magnus Hagander
Date:
Subject: Re: My honours project - databases using dynamically attached entity-properties