On Fri, May 9, 2014 at 7:01 PM, Fujii Masao <masao.fu...@gmail.com> wrote: > On Fri, May 9, 2014 at 1:06 PM, Amit Kapila <amit.kapil...@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 -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers