From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: server auto-restarts and ipcs |
Date: | 2004-11-09 23:35:34 |
Message-ID: | 6417.1100043334@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> I noticed that ipcs on my linux box has a command-line option to list the
> pid that created the segment. Not sure if such a library exists in usable
> form, but looking for segments owned by the downed postmaster's pid would
> seem to be what is needed. Just a thought...
[ thinks about it... ] Nah, it's still not bulletproof, because in a
system reboot situation you can't trust the old PID either. It could
easy be that the other guy gets both the PID and the shmem ID that
belonged to you last time.
I've committed changes for 8.0 that mark a shmem segment with the inode
of the associated data directory; that should be a stable enough ID to
handle all routine-reboot cases. (If you had to restore your whole
filesystem from backup tapes, it might be wrong, but you're going to be
doing such recovery manually anyway ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Wheeler | 2004-11-09 23:56:29 | ANNOUNCE: Bricolage 1.8.3 |
Previous Message | Ed L. | 2004-11-09 23:28:01 | Re: server auto-restarts and ipcs |
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2004-11-10 00:20:47 | Re: server auto-restarts and ipcs |
Previous Message | Ed L. | 2004-11-09 23:28:01 | Re: server auto-restarts and ipcs |