Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values
| От | Gregory Stark |
|---|---|
| Тема | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| Дата | |
| Msg-id | 87abyiosic.fsf@stark.xeocode.com обсуждение исходный текст |
| Ответ на | Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [COMMITTERS] pgsql: Make configuration parameters
fall back to their default values
Re: [COMMITTERS] pgsql: Make configuration parameters fall back to their default values |
| Список | pgsql-hackers |
"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? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: