Re: Postgresql 9.1 pg_last_xact_replay_timestamp limitations

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Gabi Julien <gabi(dot)julien(at)broadsign(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql 9.1 pg_last_xact_replay_timestamp limitations
Date: 2010-12-08 02:58:56
Message-ID: AANLkTi=2_OKfRdroCDMWGs8ysREzQ12B6aNX3_Dg7MZW@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 8, 2010 at 1:31 AM, Gabi Julien <gabi(dot)julien(at)broadsign(dot)com> wrote:
> pg_last_xact_replay_timestamp() returns null when the server is restarted until a new transaction is streamed to the hot standby server. It might take a long time before this happens. Because of this, we can't rely this function completely.

I couldn't reproduce this. Could you provide a self-contained test case?

Regards,

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2010-12-08 05:09:25 Re: Abusing Postgres in interesting ways
Previous Message James B. Byrne 2010-12-08 02:48:21 Re: PG84 and SSL on CentOS-5.5 was PG84 and SELinux