Re: pg_last_xlog_receive_location() - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: pg_last_xlog_receive_location()
Date
Msg-id AANLkTinhXrbvoAjG7EWgjfWjzLyLbOR66VCiYp5kOA9m@mail.gmail.com
Whole thread Raw
In response to pg_last_xlog_receive_location()  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: pg_last_xlog_receive_location()
List pgsql-hackers
On Wed, Mar 30, 2011 at 10:13 AM, Tatsuo Ishii <ishii@postgresql.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


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Triggers on system catalog
Next
From: Tatsuo Ishii
Date:
Subject: Re: pg_last_xlog_receive_location()