Postgres Pro
Downloads
Home   >   mailing lists

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

From Fujii Masao
Subject Re: track_commit_timestamp and COMMIT PREPARED
Date
Msg-id CAHGQGwFLYW55-eKoapG7LVrTpOj-9ttPer_XLwkOuD7yQoxAWw@mail.gmail.com
Whole thread Raw
In response to Re: track_commit_timestamp and COMMIT PREPARED  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: track_commit_timestamp and COMMIT PREPARED  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Wed, Aug 5, 2015 at 2:16 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> 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.

Yep, added.

Regards,

-- 
Fujii Masao

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore
Next
From: Tom Lane
Date:
Subject: Re: Hooking at standard_join_search (Was: Re: Foreign join pushdown vs EvalPlanQual)