Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-bugs-owner+M39263=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
 id 1XAQqI-0005CH-99
 for pgsql-bugs@arkaria.postgresql.org; Thu, 24 Jul 2014 21:46:26 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-bugs-owner+M39263=pgsql+2Dbugs=arkaria.postgresql.org@postgresql.org>)
 id 1XAQqH-0000cN-10
 for pgsql-bugs@arkaria.postgresql.org; Thu, 24 Jul 2014 21:46:25 +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 <tgl@sss.pgh.pa.us>) id 1XAQqF-0000cE-Vk
 for pgsql-bugs@postgresql.org; Thu, 24 Jul 2014 21:46:24 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
 by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <tgl@sss.pgh.pa.us>) id 1XAQq9-0004xK-0r
 for pgsql-bugs@postgresql.org; Thu, 24 Jul 2014 21:46:22 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
 by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s6OLkD3i020430;
 Thu, 24 Jul 2014 17:46:13 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: s.zuban@gmail.com
cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #11032: Prepared transactions do not update
 pg_last_xact_replay_timestamp() anymore
In-reply-to: <20140724191127.32089.82261@wrigleys.postgresql.org>
References: <20140724191127.32089.82261@wrigleys.postgresql.org>
Comments: In-reply-to s.zuban@gmail.com
 message dated "Thu, 24 Jul 2014 19:11:27 -0000"
Date: Thu, 24 Jul 2014 17:46:13 -0400
Message-ID: <20429.1406238373@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
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

s.zuban@gmail.com writes:
> After upgrade from 9.3.4 to 9.3.5 pg_last_xact_replay_timestamp() returns
> outdated timestamp.

> It stopped working properly after commit 
> d19bd29f07aef9e508ff047d128a4046cc8bc1e2

Really?

It looks to me like this never worked: the code around recoveryStopsHere
has never paid any attention to COMMIT_PREPARED (or ABORT_PREPARED).
Certainly that patch had zip to do with the replay-timestamp behavior.

If you think it worked before, I'd like to see what your test case was.

			regards, tom lane


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