Tom Lane wrote:
Jon Lapham <[EMAIL PROTECTED]> writes:
I recently had another electrical power outage that left my machine
unable to restart postgresql. I had previously reported this a while ago:
http://archives.postgresql.org/pgsql-general/2005-04/msg01286.php
Anyway, because I have seen this problem before, I knew exactly what the
solution to the problem was (delete the postmaster.pid file),
As was pointed out to you in the discussion subsequent to that message,
this is not a good automatic response, and it should not be necessary at
all with a post-8.0 postmaster.
Okay, yes, I forgot to mention that I also checked to make sure there
was no postmaster running (via "ps").
FATAL: pre-existing shared memory block (key 5432001, ID 65536) is
still in use
This is extremely odd, because a shared memory block could not possibly
have survived a reboot. Too bad you have destroyed the evidence,
because I would like to know what really happened there. Is it possible
that you have somehow managed to try to start the postmaster twice
during your system boot cycle? If you do have two postmasters running
in that data directory right now, you are in deep trouble :-(
Ugh, I should have sent the email before "fixing" the problem. Sorry
about that. If it happens again, I will not be so hasty. Luckily (for
you, not me) we have frequent power outages where this computer resides.
:) Maybe it will happen again.
I do not *think* I am running 2 postmasters.
[EMAIL PROTECTED] ~]# service postgresql stop
Stopping postgresql service: [ OK ]
[EMAIL PROTECTED] ~]# ps -A | grep -i post
[EMAIL PROTECTED] ~]# service postgresql start
Starting postgresql service: [ OK ]
[EMAIL PROTECTED] ~]# ps -A | grep -i post
30760 ? 00:00:00 postmaster
30762 ? 00:00:00 postmaster
30764 ? 00:00:00 postmaster
30765 ? 00:00:00 postmaster
30766 ? 00:00:00 postmaster
...is that normal to see 5 of them running?
I'm running just the standard (up to date) Fedora Core 5 version of
postgresql, init scripts and all.
I can reproduce this problem in v8.1.4 by these simple steps:
This is not "reproducing the problem", this is merely demonstrating that
the postmaster will fail to overwrite a root-owned postmaster.pid file.
Okay.
--
-**-*-*---*-*---*-*---*-----*-*-----*---*-*---*-----*-----*-*-----*---
Jon Lapham <[EMAIL PROTECTED]> Rio de Janeiro, Brasil
Personal: http://www.jandr.org/
***-*--*----*-------*------------*--------------------*---------------
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
