Re: How can we tell how far behind the standby is?

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: How can we tell how far behind the standby is?
Date: 2010-11-09 14:16:03
Message-ID: AANLkTi=zK2PPrOk9KL=wdtmjfSF1i4KEPdKCyBHFHD6+@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 9, 2010 at 7:57 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> The patch which I'm proposing is helpful for you?
>> http://archives.postgresql.org/pgsql-hackers/2010-11/msg00167.php
>
> Depends.  Is that the timestamp on the master (when it was synced), or
> the timestamp on the standby (when it was replayed)?  It's only helpful
> if it's the former.

It's the former. The function which I'm proposing returns the timestamp
of the last replayed commit/abort log record. That timestamp is given
when the commit/abort log record is generated in the master.

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-09 14:23:25 Re: CLUSTER can change t_len
Previous Message Euler Taveira de Oliveira 2010-11-09 14:06:55 pg_ctl init doc bug