Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDY3u-0000FY-N8 for pgsql-general@arkaria.postgresql.org; Wed, 24 May 2017 15:18:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dDY3t-00029G-Kg for pgsql-general@arkaria.postgresql.org; Wed, 24 May 2017 15:18:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dDY3s-00028E-IT for pgsql-general@postgresql.org; Wed, 24 May 2017 15:18:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dDY3p-0000lr-PG for pgsql-general@postgresql.org; Wed, 24 May 2017 15:18:55 +0000 Received: from pro.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v4OFImLO016946; Wed, 24 May 2017 11:18:48 -0400 From: Tom Lane To: y39chen cc: pgsql-general@postgresql.org Subject: Re: Is there possibility btree_redo with XLOG_BTREE_DELETE done between standby_redo and the end of backup In-reply-to: <1495609157661-5963011.post@n3.nabble.com> References: <1495609157661-5963011.post@n3.nabble.com> Comments: In-reply-to y39chen message dated "Tue, 23 May 2017 23:59:17 -0700" Date: Wed, 24 May 2017 11:18:48 -0400 Message-ID: <2253.1495639128@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org y39chen writes: > is there possibility btree_redo with XLOG_BTREE_DELETE info done between > standby_redo and the end of backup? I have PostgreSQL 9.3.14 which have > some patches to use and easy to happen. > ... > //inconsistent detected in btree_xlog_delete_get_latestRemovedXid() > [26005-59251d35.6595-726087] 2017-05-24 05:42:22.513 GMT < > WARNING: > 01000: btree_xlog_delete_get_latestRemovedXid: cannot operate with > inconsistent data This looks a whole lot like a bug we fixed in 9.3.15, cf https://www.postgresql.org/message-id/flat/DB5PR07MB15416C65687A1EA9AC0D26F8D6E00%40DB5PR07MB1541.eurprd07.prod.outlook.com regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general