Re: Bug in visibility map WAL-logging - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Bug in visibility map WAL-logging
Date
Msg-id CAM-w4HO6dHBgkgcwJwVo_7_r6WTA8HM1T5DTQzwJAg6w2iWWnA@mail.gmail.com
Whole thread Raw
In response to Re: Bug in visibility map WAL-logging  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Bug in visibility map WAL-logging  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On Tue, Jan 7, 2014 at 11:36 AM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> Hmm. The xlogdump indeed shows that the order of 'clean' and 'visible' is
> incorrect, but I don't immediately see how that could cause the PANIC. Why
> is the page uninitialized in the standby? If VACUUM is removing some dead
> tuples from it, it certainly should exist and be correctly initialized.


Unless the vacuum subsequently truncated the file to be shorter and
the backup was taken after that?

-- 
greg



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Standalone synchronous master
Next
From: Craig Ringer
Date:
Subject: Re: WIP patch (v2) for updatable security barrier views