Re: wal_consistency_checking reports an inconsistency on master branch

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: wal_consistency_checking reports an inconsistency on master branch
Date: 2018-04-12 22:36:12
Message-ID: CAH2-Wzm9fPb3v+Vx9mJ_t8d6OASUhQppMsq0J86d_FNrHhWJzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 12, 2018 at 11:47 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> In short, it looks like the tests added to update.sql by commit
> 2f178441 ("Allow UPDATE to move rows between partitions") lead to this
> failure, since I always hit a problem when update.sql is reached. I
> haven't gone to the trouble of digging any deeper than that just yet.

Without having looked at it in much detail, this seems rather more
likely to be the fault of 2f178441. That was recent enough that it's
easy to believe that I'd be the first to notice it, and actually has
on-disk changes, in the form of ItemPointerSetMovedPartitions().

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-04-12 22:46:27 Re: Instability in partition_prune test?
Previous Message Thomas Munro 2018-04-12 22:29:25 Instability in partition_prune test?