Thom Brown <t...@linux.com> writes:
> The log contains a misleading output following the removal of the pid file:
> 2015-10-09 15:39:32 BST [31507]: [4-1] user=,db=,client= LOG: could
> not open file "postmaster.pid": No such file or directory
> 2015-10-09 15:39:32 BST [31507]: [5-1] user=,db=,client= LOG:
> performing immediate shutdown because data directory lock file is
> invalid
> 2015-10-09 15:39:32 BST [31507]: [6-1] user=,db=,client= LOG:
> received immediate shutdown request
> 2015-10-09 15:39:32 BST [31556]: [1-1] user=,db=,client= WARNING:
> terminating connection because of crash of another server process
> 2015-10-09 15:39:32 BST [31556]: [2-1] user=,db=,client= DETAIL: The
> postmaster has commanded this server process to roll back the current
> transaction and exit, because another server process exited abnormally
> and possibly corrupted shared memory.
> 2015-10-09 15:39:32 BST [31556]: [3-1] user=,db=,client= HINT: In a
> moment you should be able to reconnect to the database and repeat your
> command.
Looks as-expected to me. We're forcing a panic stop.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
