Re: Unhelpful initdb error message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thom Brown <thom(at)linux(dot)com>
Cc: Bosco Rama <postgres(at)boscorama(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Unhelpful initdb error message
Date: 2012-03-06 19:28:18
Message-ID: 3906.1331062098@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thom Brown <thom(at)linux(dot)com> writes:
> On 6 March 2012 18:20, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Still, I agree with your point: Thom should reboot and see if the
>> misbehavior is still there, because that would be useful info for his
>> bug report.

> After a reboot, initdb completes successfully. I don't think it
> performed an fsck of any kind as I don't see it in the logs.

Fascinating. So maybe there is something to Bosco's theory of something
holding open the old pidfile. But what would that be? The postmaster
doesn't hold it open, just write it and close it.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andre Lopes 2012-03-06 19:30:24 Complex transactions without using plPgSQL Functions. It is possible?
Previous Message Thom Brown 2012-03-06 19:00:08 Re: Unhelpful initdb error message