Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore
Date
Msg-id 20140724215743.GG16857@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore
List pgsql-bugs
On 2014-07-24 17:46:13 -0400, Tom Lane wrote:
> 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.

I wonder if this is possibly influenced by
bb38fb0d43c8d7ff54072bfd8bd63154e536b384. IIRC before it committing a
prepared xact caused a plain commit record for the xid doing the COMMIT
PREPARED.

Greetings,

Andres Freund

--
 Andres Freund                       http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore
Next
From: Tom Lane
Date:
Subject: Re: BUG #11032: Prepared transactions do not update pg_last_xact_replay_timestamp() anymore