Skip site navigation (1) Skip section navigation (2)

pgsql: Change pg_last_xlog_receive_location() not to move backwards.Th

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Change pg_last_xlog_receive_location() not to move backwards.Th
Date: 2011-03-01 18:57:51
Message-ID: (view raw or whole thread)
Lists: pgsql-committers
Change pg_last_xlog_receive_location() not to move backwards. That makes
it a lot more useful for determining which standby is most up-to-date,
for example. There was long discussions on whether overwriting existing
existing WAL makes sense to begin with, and whether we should do some more
extensive variable renaming, but this change nevertheless seems quite

Fujii Masao, reviewed by Jeff Janes, Robert Haas, Stephen Frost.



Modified Files
doc/src/sgml/func.sgml                     |    6 ++----
src/backend/replication/walreceiver.c      |    9 ++++++---
src/backend/replication/walreceiverfuncs.c |   13 +++++++++++--
src/include/replication/walreceiver.h      |   14 ++++++++++----
4 files changed, 29 insertions(+), 13 deletions(-)

pgsql-committers by date

Next:From: User FxjrDate: 2011-03-01 21:09:28
Subject: npgsql - Npgsql2: In Multi-threaded applications there is a race
Previous:From: Heikki LinnakangasDate: 2011-03-01 17:06:48
Subject: pgsql: Fix bugs in Serializable Snapshot Isolation.

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group