Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)heroku(dot)com>
Subject: Re: Another possible corruption bug in 9.3.2 or possibly a known MultiXact problem?
Date: 2014-02-28 06:19:14
Message-ID: 20140228061914.GB15628@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-02-27 23:41:08 +0000, Greg Stark wrote:
> Though I notice something I can't understand here.
>
> After activating the new clone subsequent attempts to select rows from
> the page bump the LSN, presumably due to touching hint bits (since the
> prune xid hasn't changed). But the checksum hasn't changed even after
> running CHECKPOINT.

Are you running with full_page_writes=off?

Only delete and update do a PageSetPrunable(), so prune_xid not being
changed doesn't say much...

> How is it possible for the LSN to get updated without changing the checksum?

Generally the LSN is computed when writing, not when a buffer is
modified, so that's not particularly surprising. It'd be interesting to
see what the records are that end on those LSNs.

It'd probably nice to add the capability to dump records that end in a
particular location to pg_xlogdump...

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christophe Pettus 2014-02-28 07:02:21 Re: jsonb and nested hstore
Previous Message Andres Freund 2014-02-28 06:12:02 Re: jsonb and nested hstore