Re: pg_last_xlog_receive_location()

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_last_xlog_receive_location()
Date: 2011-03-30 01:41:51
Message-ID: AANLkTinhXrbvoAjG7EWgjfWjzLyLbOR66VCiYp5kOA9m@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 30, 2011 at 10:13 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> In my understanding pg_last_xlog_receive_location() returns NULL if
> applied to non standby server:
>
> Get last transaction log location received and synced to disk by
> streaming replication. While streaming replication is in progress this
> will increase monotonically. But when streaming replication is
> restarted this will back off to the replication starting position,
> typically the beginning of the WAL file containing the current replay
> location. If recovery has completed this will remain static at the
> value of the last WAL record received and synced to disk during
> recovery. If streaming replication is disabled, or if it has not yet
> started, the function returns NULL.
>
> However my primary server returns non NULL. Am I missing something?

In the primary server which was brought up from the standby,
pg_last_xlog_receive_location() returns non-NULL.

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 Tatsuo Ishii 2011-03-30 02:08:33 Re: pg_last_xlog_receive_location()
Previous Message Stephen Frost 2011-03-30 01:40:00 Re: Triggers on system catalog