Re: page corruption on 8.3+ that makes it to standby - Mailing list pgsql-hackers

From Robert Haas
Subject Re: page corruption on 8.3+ that makes it to standby
Date
Msg-id AANLkTikZBEs2evBXgyo4D7L82K7U02ULBymEFLZNmtk6@mail.gmail.com
Whole thread Raw
In response to Re: page corruption on 8.3+ that makes it to standby  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Wed, Jul 28, 2010 at 3:08 PM, Jeff Davis <pgsql@j-davis.com> wrote:
> On Wed, 2010-07-28 at 14:50 -0400, Robert Haas wrote:
>> It seems like if log_newpage() were to set the LSN/TLI before calling
>> XLogInsert() - or optionally not - then it wouldn't be necessary to
>> set them also in heap_xlog_newpage(); the memcpy operation would by
>> definition have copied the right information onto the page.  That
>> seems like it would be a cleaner design, but back-patching a change to
>> the interpretation of WAL records that might already be on someone's
>> disk seems dicey at best.
>
> How do you set the LSN before XLogInsert()?

Details, details...

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: page corruption on 8.3+ that makes it to standby
Next
From: Tom Lane
Date:
Subject: Re: page corruption on 8.3+ that makes it to standby