From 6eba5a7c57d1d61f46b6966026bf7bc07f8e087c Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Tue, 1 Mar 2011 20:46:57 +0200 Subject: 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 uncontroversial. Fujii Masao, reviewed by Jeff Janes, Robert Haas, Stephen Frost. --- doc/src/sgml/func.sgml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 679f856b9ce..5ccece26001 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -14179,10 +14179,8 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup()); text Get last transaction log location received and synced to disk by streaming replication. While streaming replication is in progress - this will increase monotonically. But when streaming replication is - restarted this will back off to the replication starting position, - typically the beginning of the WAL file containing the current - replay location. If recovery has completed this will remain static at + this will increase monotonically. If recovery has completed this will + remain static at the value of the last WAL record received and synced to disk during recovery. If streaming replication is disabled, or if it has not yet started, the function returns NULL. -- cgit v1.2.3