Re: Database Corruption ? - Mailing list pgsql-general

From Chris Stokes
Subject Re: Database Corruption ?
Date
Msg-id 39EA496EA6D5564B8FFAE48395CEB3D048B4@mail.melb.basssoftware.com
Whole thread Raw
In response to Database Corruption ?  ("Chris Stokes" <ChrisS@BassSoftware.com>)
Responses Re: Database Corruption ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thanks Tom,

We use the RPM installation, if I do and rpm -Uvh for the packages to upgrade to the new 7.3.4 will that be sufficient
ordoes it require some sort of database upgrade or unload/reload? 

Thanks
Chris

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, 14 November 2003 11:08 AM
To: Chris Stokes
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Database Corruption ?


"Chris Stokes" <ChrisS@BassSoftware.com> writes:
> PANIC:  XLogWrite: write request 1/812D0000 is past end of log 1/812D0000

This sure looks like the symptom of the 7.3.3 failure-to-restart bug.
If you are on 7.3.3 then an update to 7.3.4 will fix it.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Database Corruption ?
Next
From: Tom Lane
Date:
Subject: Re: Database Corruption ?