From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: timestamp of the last replayed transaction |
Date: | 2010-11-04 01:27:33 |
Message-ID: | AANLkTimYnzF5vU=cZgmZU7a61UmmaREM4Z6u39BCF5OR@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 2, 2010 at 10:38 PM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
>> After 9.0 release, I've often heard that some people want to know
>> how far transactions have been replayed in the standby in timestamp
>> rather than LSN. So I'm thinking to include the function which returns
>> the timestamp of the last applied transaction (i.e., commit/abort WAL
>> record) in the core.
>>
>> Name: pg_last_replay_xact_timestamp (better name?)
>> Return Type: timestamp with time zone
>>
>> Thought?
>
> How do you want to implement the tracking?
I'm thinking to just expose GetLatestXTime(), i.e., XLogCtl->recoveryLastXTime.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Itagaki Takahiro | 2010-11-04 01:45:14 | Re: Comparison with "true" in source code |
Previous Message | Dimitri Fontaine | 2010-11-03 21:32:25 | Re: ALTER OBJECT any_name SET SCHEMA name |