Tom Lane wrote: > "David Schweikert" <[EMAIL PROTECTED]> writes: > > pg_ctl doesn't work if you put postgresql.conf in a different directory than > > the database data files. > > Yeah, this is a known limitation that seems unlikely to get fixed soon, > as doing it right would appear to require giving pg_ctl the ability to > parse the config file completely.
FYI, it is a TODO item: * Allow pg_ctl to work properly with configuration files located outside the PGDATA directory pg_ctl can not read the pid file because it isn't located in the config directory but in the PGDATA directory. The solution is to allow pg_ctl to read and understand postgresql.conf to find the data_directory value. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your Subscription: http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-bugs
