From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Fix PID file location? |
Date: | 2005-05-13 18:06:03 |
Message-ID: | 200505131106.03311.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
FOlks,
> The problem seems to be that pg_ctl expects the PID file to be in $PGDATA,
> but the file actually gets written by the postmaster to the actual data
> directory. You can work around this by setting "external_pid_file", but
> this then prevents you from using external_pid_file for another purpose.
More about this: due to the PID file not being in the right place, pg_ctl stop
never reports success:
waiting for postmaster to shut
down............................................................... failed
pg_ctl: postmaster does not shut down
This appears to be because the duplicate PID in the conf directory is not
removed on shutdown.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-05-13 18:34:53 | Re: Catalog Security WAS: Views, views, views: Summary |
Previous Message | Andrew - Supernews | 2005-05-13 17:50:56 | Re: Catalog Security WAS: Views, views, views: Summary of Arguments |
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Ten | 2005-05-13 23:01:48 | Re: patches for items from TODO list |
Previous Message | Tom Lane | 2005-05-13 16:48:51 | Re: Micro doc patch |