v7.3.4 Bug Fix Release

Started by The Hermit Hackerover 22 years ago5 messagesgeneral
Jump to latest
#1The Hermit Hacker
scrappy@hub.org

In order to address a potentially serious (although rare) server startup
failure that was recently reported, we have just bundled up and put onto
the ftp sites v7.3.4 of PostgreSQL ...

It is a recommended upgrade, and does not require a dump/restore of your
existing databases to put into place.

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: The Hermit Hacker (#1)
Re: [ANNOUNCE] v7.3.4 Bug Fix Release

The Hermit Hacker <scrappy@hub.org> writes:

In order to address a potentially serious (although rare) server startup
failure that was recently reported, we have just bundled up and put onto
the ftp sites v7.3.4 of PostgreSQL ...

BTW, it should be mentioned that the startup failure was introduced in
7.3.3. If you are running 7.3.3, I recommend that you consider this an
urgent upgrade. If you are running an older version then it is not urgent.

regards, tom lane

#3Joseph Shraibman
jks@selectacast.net
In reply to: Tom Lane (#2)
Re: [ANNOUNCE] v7.3.4 Bug Fix Release

Tom Lane wrote:

The Hermit Hacker <scrappy@hub.org> writes:

In order to address a potentially serious (although rare) server startup
failure that was recently reported, we have just bundled up and put onto
the ftp sites v7.3.4 of PostgreSQL ...

BTW, it should be mentioned that the startup failure was introduced in
7.3.3. If you are running 7.3.3, I recommend that you consider this an
urgent upgrade. If you are running an older version then it is not urgent.

Is this an example of the startup failure?

LOG: database system shutdown was interrupted at 2003-07-27 21:46:13 EDT
LOG: checkpoint record is at 0/52BB1FC0
LOG: redo record is at 0/52BB1FC0; undo record is at 0/0; shutdown FALSE
LOG: next transaction id: 1198743; next oid: 1702650
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: ReadRecord: unexpected pageaddr 0/4DBB2000 in log file 0, segment
82, offset 12263424
LOG: redo is not required
PANIC: XLogWrite: write request 0/52BB2000 is past end of log 0/52BB2000
LOG: startup process (pid 688) was terminated by signal 6
LOG: aborting startup due to startup process failure

#4Joseph Shraibman
jks@selectacast.net
In reply to: Joseph Shraibman (#3)
Re: [ANNOUNCE] v7.3.4 Bug Fix Release

Joseph Shraibman wrote:

Is this an example of the startup failure?

LOG: database system shutdown was interrupted at 2003-07-27 21:46:13 EDT
LOG: checkpoint record is at 0/52BB1FC0
LOG: redo record is at 0/52BB1FC0; undo record is at 0/0; shutdown FALSE
LOG: next transaction id: 1198743; next oid: 1702650
LOG: database system was not properly shut down; automatic recovery in
progress
LOG: ReadRecord: unexpected pageaddr 0/4DBB2000 in log file 0, segment
82, offset 12263424
LOG: redo is not required
PANIC: XLogWrite: write request 0/52BB2000 is past end of log 0/52BB2000
LOG: startup process (pid 688) was terminated by signal 6
LOG: aborting startup due to startup process failure

In any case it started right up after I installed 7.3.4

#5Tom Lane
tgl@sss.pgh.pa.us
In reply to: Joseph Shraibman (#3)
Re: [ANNOUNCE] v7.3.4 Bug Fix Release

Joseph Shraibman <jks@selectacast.net> writes:

Is this an example of the startup failure?

PANIC: XLogWrite: write request 0/52BB2000 is past end of log 0/52BB2000

Yup.

You should be able to get out of the problem with pg_resetxlog.

regards, tom lane