Skip site navigation (1) Skip section navigation (2)

Re: timestamp of the last replayed transaction

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-05 01:00:41
Message-ID: AANLkTikPivuROTFR466ji0Q44WgtTna02jbGT=0_zYE3@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Nov 4, 2010 at 10:27 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> 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.

I attached the patch.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment: pg_last_replay_xact_timestamp_v1.patch
Description: application/octet-stream (3.3 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-11-05 02:59:10
Subject: Re: plan time of MASSIVE partitioning ...
Previous:From: Alvaro HerreraDate: 2010-11-04 21:57:33
Subject: Re: ALTER OBJECT any_name SET SCHEMA name

Privacy Policy | About PostgreSQL
Copyright © 1996-2013 The PostgreSQL Global Development Group