Re: Unhelpful initdb error message

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

Bosco Rama <postgres(at)boscorama(dot)com> writes:
> Thom Brown wrote:
>> I've done that a couple times, but no effect. I think Tom's point
>> about a filesystem bug is probably right.

> Have you rebooted since this started? There may be a process that is
> holding the pid file 'deleted but present' until the process terminates.

Even if something is holding the file open, that wouldn't prevent unlink
from removing the directory entry for it; or even if we were talking
about a badly-designed filesystem that failed to follow standard Unix
semantics, that wouldn't explain why the directory entry is apparently
visible to some operations but not others.

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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Raymond O'Donnell 2012-03-06 18:25:34 Re: Adding a lot of tables
Previous Message Bosco Rama 2012-03-06 18:12:50 Re: Unhelpful initdb error message