Re: timestamp of the last replayed transaction

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: timestamp of the last replayed transaction
Date: 2010-11-08 11:00:50
Message-ID: AANLkTimc1-29eiwWbFCZohmXYOOPG1r0Z4k8Y=baKwzR@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 6, 2010 at 9:58 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> This looks good, but how about adding:
>
> if (!RecoveryInProgress())
>    PG_RETURN_NULL();
>
> Otherwise, if we're in Hot Standby mode for a while and then enter
> normal running, wouldn't this still return a (stale) value?

Yes, but isn't that (stale) value useful to check how far WAL records
have been replayed, *after failover*?

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 Fujii Masao 2010-11-08 11:05:42 Re: How can we tell how far behind the standby is?
Previous Message Andrew Dunstan 2010-11-08 10:03:15 Re: [Pgbuildfarm-members] Buildfarm client version 4.3 released