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

From Simon Riggs
Subject Re: page corruption on 8.3+ that makes it to standby
Date
Msg-id 1280393904.1878.8922.camel@ebony
Whole thread Raw
In response to Re: page corruption on 8.3+ that makes it to standby  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: page corruption on 8.3+ that makes it to standby
List pgsql-hackers
On Wed, 2010-07-28 at 14:22 -0700, Jeff Davis wrote:
> On Wed, 2010-07-28 at 15:37 -0400, Tom Lane wrote:
> > So nevermind that distraction.  I'm back to thinking that fix1 is
> > the way to go.
> 
> Agreed.
> 
> It's uncontroversial to have a simple guard against corrupting an
> uninitialized page, and uncontroversial is good for things that will be
> back-patched.

Still don't understand why we would not initialize such pages. If we're
copying a relation we must know enough about it to init a page.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: including backend ID in relpath of temp rels - updated patch
Next
From: Matthew Wakeling
Date:
Subject: Re: [JDBC] Trouble with COPY IN