Re: page corruption on 8.3+ that makes it to standby
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2010-07-28T17:28:23Z
Lists: 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