Re: [GENERAL] Understanding pg_last_xlog_receive_location

2017-03-03 Thread Zach Walton
quier wrote: > On Thu, Mar 2, 2017 at 5:53 AM, Zach Walton wrote: > > 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_re

Re: [GENERAL] Understanding pg_last_xlog_receive_location

2017-03-01 Thread Zach Walton
---+---+-- t | | 0/3000198 On Wed, Mar 1, 2017 at 11:17 AM, Zach Walton 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 repor

Re: [GENERAL] Understanding pg_last_xlog_receive_location

2017-03-01 Thread Zach Walton
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.

[GENERAL] Understanding pg_last_xlog_receive_location

2017-02-28 Thread Zach Walton
I'm following the documentation here (using postgresql 9.4.5): https://www.postgresql.org/docs/9.4/static/functions-admin.html I'm attempting to fully understand the interplay between pg_is_in_recovery() + pg_last_xlog_receive_location() + pg_last_xlog_replay_location() so we can devise a reliable