Re: postgresql.auto.conf read from wrong directory
От | Amit Kapila |
---|---|
Тема | Re: postgresql.auto.conf read from wrong directory |
Дата | |
Msg-id | CAA4eK1++zddo3pjaPUeynuH+ojz-TSHOv2LGycF9Aow8BFVr1A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: postgresql.auto.conf read from wrong directory (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: postgresql.auto.conf read from wrong directory
|
Список | pgsql-hackers |
On Fri, May 9, 2014 at 7:01 PM, Fujii Masao <masao.fujii@gmail.com> wrote: > On Fri, May 9, 2014 at 1:06 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> There is no harm in forbidding data_directory, but similarly we can >> imagine that people can set some very large values for some config >> variables due to which later it can have symptoms similar to this >> issue. > > Yes, that can prevent the server from restarting at all. In this case, > to restart the server, we need to edit postgresql.auto.conf manually > and remove the problematic settings though the header of > postgresql.auto.conf warns "Do not edit this file manually!". So lets not try to forbid data_directory in postgresql.auto.conf and just fix the case reported in this mail for postgresql.conf for which the patch is attached upthread. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: