Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values
От | Magnus Hagander |
---|---|
Тема | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
Дата | |
Msg-id | 20070313084443.GC22636@svr2.hagander.net обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values ("Andrew Dunstan" <andrew@dunslane.net>) |
Ответы |
Re: [COMMITTERS] pgsql: Make configuration parameters fall
back to their default values
|
Список | 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 по дате отправления: