From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Perform an immediate shutdown if the postmaster.pid file is remo |
Date: | 2015-10-09 20:58:06 |
Message-ID: | 47566.1444424286@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Thom Brown <thom(at)linux(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2015-10-09 21:04:48 | Re: pgsql: Perform an immediate shutdown if the postmaster.pid file is remo |
Previous Message | Robert Haas | 2015-10-09 19:11:37 | pgsql: Make abbreviated key comparisons for text a bit cheaper. |