Postgres Pro
Downloads
Home   >   mailing lists

Re: track_commit_timestamp and COMMIT PREPARED - Mailing list pgsql-hackers

From Robert Haas
Subject Re: track_commit_timestamp and COMMIT PREPARED
Date
Msg-id CA+TgmobONXRca2mZTm4GfFhBWg-acZ-hQhFDQLUaU_AGjgfRGg@mail.gmail.com
Whole thread Raw
In response to track_commit_timestamp and COMMIT PREPARED  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: track_commit_timestamp and COMMIT PREPARED
Re: track_commit_timestamp and COMMIT PREPARED
List pgsql-hackers
Tree view 
On Mon, Aug 3, 2015 at 10:31 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> track_commit_timestamp tracks COMMIT PREPARED as expected in standby server,
> but not in master server. Is this intentional? It should track COMMIT PREPARED
> even in master? Otherwise, we cannot use commit_timestamp feature to check
> the replication lag properly while we use 2PC.

That sounds like it must be a bug.  I think you should add it to the
open items list.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Next
From: Andres Freund
Date:
Subject: Re: track_commit_timestamp and COMMIT PREPARED