From: | Mathieu De Zutter <mathieu(at)dezutter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4913: Row missing from primary key index |
Date: | 2009-07-10 16:37:15 |
Message-ID: | d4468d970907100937n3b1efa43l2fa39f4831966326@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jul 10, 2009 at 6:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> As far as anyone knows, it's impossible to get into the
> disconnected-backends state unless (a) you manually remove the
> postmaster.pid file that provides the interlock against it, or
> (b) you're trying to run multiple copies of Postgres on different
> machines that're sharing an NFS or SAN mount of the same database files.
> I assume you'd have mentioned it if you were trying (b), but I wonder
> whether you have an init script that takes it on itself to remove the
> postmaster.pid file? It's generally considered irresponsible for an
> init script to do that, but I'm not sure every distro has gotten the word.
>
(a) I can't remember doing that, but who knows I got frustrated at some
point in time and took a wrong shortcut.
(b) I've only got local RAID storage.
I've checked the debian init script, and the only thing related to the pid
file I found was creating the underlying directory /var/run/postgresql
Regards,
Mathieu
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Neill | 2009-07-10 23:37:46 | BUG #4916: wish: more statistical functions (median, percentiles etc) |
Previous Message | Alvaro Herrera | 2009-07-10 16:31:05 | Re: BUG #4914: uuid_generate_v4 not present in eithersource or yum/rpm |