From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Zach Walton <zacwalt(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Understanding pg_last_xlog_receive_location |
Date: | 2017-03-01 05:47:00 |
Message-ID: | CAB7nPqRWPy=s05mXLE6i3FZsPBM6HR_AAJBjemdAzkzrSvKaqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Mar 1, 2017 at 6:51 AM, Zach Walton <zacwalt(at)gmail(dot)com> wrote:
> I'm following the documentation here (using postgresql 9.4.5):
> https://www.postgresql.org/docs/9.4/static/functions-admin.html
You should really update to a newer version of 9.4.X, you are missing
more than 1 year of bug fixes by staying on 9.4.5.
> I'm not sure I understand how this is possible. According to the docs,
> pg_last_xlog_receive_location can only be NULL when streaming is disabled
> (not the case) or hasn't started yet (doesn't seem possible when
> pg_last_xlog_replay_location is set).
>
> Could someone help shed some light on what state results in
> pg_last_xlog_receive_location being NULL when pg_last_xlog_replay_location
> is set?
That works for me for a streaming node:
=# SELECT pg_is_in_recovery(), pg_last_xlog_receive_location(),
pg_last_xlog_replay_location();
pg_is_in_recovery | pg_last_xlog_receive_location |
pg_last_xlog_replay_location
-------------------+-------------------------------+------------------------------
t | 0/30008E0 | 0/30008E0
(1 row)
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-03-01 06:30:16 | Re: [GENERAL] C++ port of Postgres |
Previous Message | Peter Eisentraut | 2017-03-01 04:42:45 | Re: [GENERAL] C++ port of Postgres |