Re: Fatal error - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Fatal error
Date
Msg-id 20050501004828.GA24028@dcc.uchile.cl
Whole thread Raw
In response to Re: Fatal error  (mmiranda@americatel.com.sv)
List pgsql-general
On Fri, Apr 29, 2005 at 10:44:53PM -0600, mmiranda@americatel.com.sv wrote:
> Tom Lane wrote:
> > mmiranda@americatel.com.sv writes:
> >> LOG:  redo starts at F1/A0A4E09C
> >> PANIC:  Invalid page header in block 68122 of 17006
> >> LOG:  startup process (pid 1959) was terminated by signal 6
> >> LOG:  aborting startup due to startup process failure
> >
> > Which PG version is this exactly?  If it's not the very latest in its
> > release series, an in-place update to the latest might help ---
> > because this looks like several known-and-fixed issues ...
>
> Postgres 7.3, i will try the upgrade tonigth,

That doesn't answer the question though, because Tom wanted to know
which of 7.3, 7.3.1, 7.3.4 etc you are running.  (You also didn't answer
the same question when I asked you.)

In the spanish list however, he disclosed that this problem happened on
a shared storage system, which is used by two postmasters on different
machines controlled by a heartbeat system.  The main server was
accidentaly disconnected from power.  I told him that concurrent
postmasters were fatal, but he hasn't confirmed whether they actually
ran concurrently.

Good luck with the upgrade, though I advise you not to use the heartbeat
system until you have really debugged it to work the way you want it to.
(Or not use it at all, and run Slony-I or some such replication system
instead.)

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Es filósofo el que disfruta con los enigmas" (G. Coli)

pgsql-general by date:

Previous
From: "Stas Oskin"
Date:
Subject: Using pgcrypto with AES-256 bits?
Next
From: Typing80wpm@aol.com
Date:
Subject: Postgresql and small office p2p networks & ODBC