| From: | Zach Walton <zacwalt(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(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 20:53:58 |
| Message-ID: | CAK-a08rKUmQJyH5QXjDDu2ULOJ0phoCQdk++Xro8yE4wYh9TJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I was able to test 9.4.11 and am seeing the same behavior:
postgres=# 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/3000198
On Wed, Mar 1, 2017 at 11:17 AM, Zach Walton <zacwalt(at)gmail(dot)com> wrote:
> Thanks. We have some patches on the 9.4.5 code base (not in the
> replication path). I'll work on porting those to 9.4.11 and will report
> back to the thread.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolai Zhubr | 2017-03-01 21:43:30 | Re: Re: Causeless CPU load waves in backend, on windows, 9.5.5 (EDB binary). |
| Previous Message | Zach Walton | 2017-03-01 19:17:02 | Re: Understanding pg_last_xlog_receive_location |