Re: Old row version in hot chain become visible after a freeze

From: Jeff Frost <jeff(at)pgexperts(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "Wood, Dan" <hexpert(at)amazon(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Old row version in hot chain become visible after a freeze
Date: 2017-09-07 03:23:28
Message-ID: 44B4A013-C188-444E-9B81-0BF351DA652F@pgexperts.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sep 6, 2017, at 6:27 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> Another thing is that if you're going through heap_copy_data, the tuple
> is only checked for DEAD, not RECENTLY_DEAD. Maybe there is no bug here
> but I'm not sure yet.

Any idea on how to identify affected rows on a running system?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2017-09-07 03:33:47 Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)?
Previous Message Michael Paquier 2017-09-07 01:23:46 Re: Old row version in hot chain become visible after a freeze