Re: track_commit_timestamp and COMMIT PREPARED

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: track_commit_timestamp and COMMIT PREPARED
Date: 2015-08-04 17:16:52
Message-ID: CA+TgmobONXRca2mZTm4GfFhBWg-acZ-hQhFDQLUaU_AGjgfRGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 3, 2015 at 10:31 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-08-04 17:18:11 Re: track_commit_timestamp and COMMIT PREPARED
Previous Message Alvaro Herrera 2015-08-04 17:15:52 Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );