Re: FATAL: bogus data in lock file "postmaster.pid": ""

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>, Michael Beattie <mtbeedee@gmail.com>, Magnus Hagander <magnus@hagander.net>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-08-27T23:35:14Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Aug 27, 2012 at 4:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Perhaps something like:
>> 
>> FATAL: lock file "foo" is empty
>> HINT: This may mean that another postmaster was starting at the
>> same time.  If not, remove the lock file and try again.

> The problem with this is that it gives the customer only one remedy,
> which they will (if experience is any guide) try whether it is
> actually correct to do so or not.

Which other remedy(s) do you think the hint should suggest?

			regards, tom lane