| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | <fabio(at)vuole(dot)me>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Proper use of pg_xlog_location_diff() |
| Date: | 2015-01-16 07:39:12 |
| Message-ID: | 54B8C020.6060902@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 1/15/15 8:41 PM, Fabio Ugo Venchiarutti wrote:
> Does it mean that pg_last_xlog_receive_location() returns the last WAL record that has been successfully "staged for replay" by the stream replication whereas pg_last_xlog_replay_location() returns the last successful WAL replay regardless of it coming from streaming or archive shipping?
> As in 2 different stages the first of which is basically irrelevant to record visibility?
(At least in -HEAD) receive is what's been committed to disk; replay is what's actually been replayed and should be visible.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-01-16 07:41:00 | Re: Simple Atomic Relationship Insert |
| Previous Message | Michael Paquier | 2015-01-16 05:52:34 | Re: can you have any idea about toast missing chunk issu resolution |