| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: page corruption on 8.3+ that makes it to standby |
| Date: | 2010-07-28 17:28:23 |
| Message-ID: | 1280338103.9421.32.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2010-07-28 18:00:35 | Re: Incorrect FTS result with GIN index |
| Previous Message | Robert Haas | 2010-07-28 17:18:54 | Re: page corruption on 8.3+ that makes it to standby |