| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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:26:10 |
| Message-ID: | 22250.1173749170@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> 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 installcheck". Make sure you have
configured --with all the PLs you want to test.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Eggyknap | 2007-03-13 05:27:37 | pgsnmpd - pgsnmpd: Fix various memory errors in pg_array.c, leaving |
| Previous Message | Andrew Dunstan | 2007-03-13 01:20:53 | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2007-03-13 01:26:15 | Re: Bitmapscan changes |
| Previous Message | Andrew Dunstan | 2007-03-13 01:20:53 | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |