| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, 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 08:44:43 |
| Message-ID: | 20070313084443.GC22636@svr2.hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Mar 12, 2007 at 08:20:53PM -0500, Andrew Dunstan wrote:
> 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
Is there any particular reason why we don't run these as part of a
general "make check"?
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-03-13 09:06:35 | pgsql: Set stderr to unbuffered for pgbench on win32. |
| Previous Message | User Eggyknap | 2007-03-13 05:27:37 | pgsnmpd - pgsnmpd: Fix various memory errors in pg_array.c, leaving |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-03-13 08:47:33 | Re: My honours project - databases using dynamically attached entity-properties |
| Previous Message | Luke Lonergan | 2007-03-13 05:16:04 | Re: Bug: Buffer cache is not scan resistant |