Re: pgsql: Fix traversal of half-frozen update chains

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Fix traversal of half-frozen update chains
Date: 2017-10-24 22:05:11
Message-ID: CAH2-WzmCLbJdJBJ9U=8a_KFMrmXmP1rBp8=t3gMn5YeHx+v9nA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Oct 17, 2017 at 3:40 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> I also realized we can stop checking (i.e. don't compare xmin to
> frozenxid) if the XMIN_FROZEN bits are set -- because in that case the
> tuple cannot possibly come from 9.3 frozen. So I think this should do
> it.

When are you planning on committing this?

--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-10-24 22:42:59 pgsql: In the planner, delete joinaliasvars lists after we're done with
Previous Message Tom Lane 2017-10-24 18:08:49 pgsql: Documentation improvements around domain types.

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-10-24 22:17:10 Re: Remove secondary checkpoint
Previous Message Peter Geoghegan 2017-10-24 21:57:47 Re: unique index violation after pg_upgrade to PG10