Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XC3Ka-0003h2-CQ for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Jul 2014 09:04:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XC3KZ-0004IZ-7e for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Jul 2014 09:04:23 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XC3KQ-000422-3h for pgsql-bugs@postgresql.org; Tue, 29 Jul 2014 09:04:14 +0000 Received: from smtp-outbound-2.vmware.com ([208.91.2.13]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XC3KK-0006Xg-Op for pgsql-bugs@postgresql.org; Tue, 29 Jul 2014 09:04:10 +0000 Received: from sc9-mailhost2.vmware.com (sc9-mailhost2.vmware.com [10.113.161.72]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id E2BAA28AC3; Tue, 29 Jul 2014 02:04:05 -0700 (PDT) Received: from EX13-CAS-012.vmware.com (EX13-CAS-012.vmware.com [10.113.191.64]) by sc9-mailhost2.vmware.com (Postfix) with ESMTP id DC516B112F; Tue, 29 Jul 2014 02:04:05 -0700 (PDT) Received: from EX13-MBX-024.vmware.com (10.113.191.44) by EX13-MBX-009.vmware.com (10.113.191.29) with Microsoft SMTP Server (TLS) id 15.0.775.38; Tue, 29 Jul 2014 02:03:59 -0700 Received: from [192.168.1.90] (10.113.160.246) by EX13-MBX-024.vmware.com (10.113.191.44) with Microsoft SMTP Server (TLS) id 15.0.775.38; Tue, 29 Jul 2014 02:03:58 -0700 Message-ID: <53D7637B.5080809@vmware.com> Date: Tue, 29 Jul 2014 12:03:55 +0300 From: Heikki Linnakangas Organization: VMware User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0 MIME-Version: 1.0 To: Tom Lane , Andres Freund CC: , Subject: Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore References: <20140724191127.32089.82261@wrigleys.postgresql.org> <20429.1406238373@sss.pgh.pa.us> <20140724215743.GG16857@alap3.anarazel.de> <21266.1406241129@sss.pgh.pa.us> <20140724223459.GI16857@alap3.anarazel.de> <21620.1406242232@sss.pgh.pa.us> <53D62059.6060304@vmware.com> In-Reply-To: <53D62059.6060304@vmware.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.160.246] X-ClientProxiedBy: EX13-CAS-013.vmware.com (10.113.191.65) To EX13-MBX-024.vmware.com (10.113.191.44) X-Pg-Spam-Score: -7.6 (-------) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org On 07/28/2014 01:05 PM, Heikki Linnakangas wrote: > I propose the attached (untested) patch that fixes the issues mentioned > this far. Committed and backpatched. - Heikki -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs