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

From Jeff Davis
Subject Re: page corruption on 8.3+ that makes it to standby
Date
Msg-id 1280338103.9421.32.camel@jdavis
Whole thread Raw
In response to Re: page corruption on 8.3+ that makes it to standby  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, 2010-07-28 at 13:18 -0400, Robert Haas wrote:
> In Jeff's original example, he crashes the database
> after extending the relation but before initializing and writing the
> new page.  I believe that at that point no XLOG has been written yet,
> so the relation has been extended but there is no WAL to be sent to
> the standby.  So now you have the exact situation you're concerned
> about - the relation has been extended on the master but not on the
> standby.  As far as I can see, this is an unavoidable consequence of
> the fact that we don't XLOG the act of extending the relation.
> Worrying about it only in the specific context of ALTER TABLE .. SET
> TABLESPACE seems backwards; if there are any bugs there, we're in for
> it.

That's a very good point. Now I'm leaning more toward your fix.

Regards,Jeff Davis



pgsql-hackers by date:

Previous
From: Robert Haas
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