Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M48693=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1dpnQf-00059E-JE
	for pgsql-bugs@arkaria.postgresql.org; Thu, 07 Sep 2017 03:24:33 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-bugs-owner+M48693=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
	id 1dpnQf-0000I0-5p
	for pgsql-bugs@arkaria.postgresql.org; Thu, 07 Sep 2017 03:24:33 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <jeff@pgexperts.com>)
	id 1dpnPw-0007Ob-PB
	for pgsql-bugs@postgresql.org; Thu, 07 Sep 2017 03:23:48 +0000
Received: from smtp66.iad3a.emailsrvr.com ([173.203.187.66])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <jeff@pgexperts.com>)
	id 1dpnPp-0002I0-Sn
	for pgsql-bugs@postgresql.org; Thu, 07 Sep 2017 03:23:48 +0000
Received: from smtp25.relay.iad3a.emailsrvr.com (localhost [127.0.0.1])
	by smtp25.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 2F3F325351;
	Wed,  6 Sep 2017 23:23:31 -0400 (EDT)
X-Auth-ID: jeff.frost@pgexperts.com
Received: by smtp25.relay.iad3a.emailsrvr.com (Authenticated sender:
 jeff.frost-AT-pgexperts.com) with ESMTPSA id 66BC625318;
	Wed,  6 Sep 2017 23:23:30 -0400 (EDT)
X-Sender-Id: jeff.frost@pgexperts.com
Received: from [10.0.1.16] (ip70-191-84-231.sb.sd.cox.net [70.191.84.231])
	(using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384)
	by 0.0.0.0:587 (trex/5.7.12);
	Wed, 06 Sep 2017 23:23:31 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Old row version in hot chain become visible after a freeze
From: Jeff Frost <jeff@pgexperts.com>
In-Reply-To: <20170906132738.2dpwvnfcuevjofhl@alvherre.pgsql>
Date: Wed, 6 Sep 2017 20:23:28 -0700
Cc: Michael Paquier <michael.paquier@gmail.com>,
 Peter Geoghegan <pg@bowt.ie>,
 "Wood, Dan" <hexpert@amazon.com>,
 "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>,
 Andres Freund <andres@anarazel.de>
Content-Transfer-Encoding: 7bit
Message-Id: <44B4A013-C188-444E-9B81-0BF351DA652F@pgexperts.com>
References: <20170906132738.2dpwvnfcuevjofhl@alvherre.pgsql>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
X-Mailer: Apple Mail (2.3273)
List-Archive: <http://archives.postgresql.org/pgsql-bugs>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-bugs.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@postgresql.org>
List-Post: <mailto:pgsql-bugs@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-bugs>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
X-Mailing-List: pgsql-bugs
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

On Sep 6, 2017, at 6:27 AM, Alvaro Herrera <alvherre@alvh.no-ip.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?


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs