Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 5c5184c

Browse files
committed
Document that receive location can rewind if replication restarts.
Fujii Masao, with some further wordsmithing by me.
1 parent 147c665 commit 5c5184c

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

doc/src/sgml/func.sgml

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.518 2010/06/10 07:00:25 heikki Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.519 2010/06/17 01:32:09 rhaas Exp $ -->
22

33
<chapter id="functions">
44
<title>Functions and Operators</title>
@@ -13282,10 +13282,13 @@ postgres=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
1328213282
<entry><type>text</type></entry>
1328313283
<entry>Get last transaction log location received and synced to disk by
1328413284
streaming replication. While streaming replication is in progress
13285-
this will increase monotonically. If recovevery has completed
13286-
this will remain static at the value of the last WAL record
13287-
received and synced to disk during recovery. If streaming replication
13288-
is disabled, or it has not yet started, the function returns NULL.
13285+
this will increase monotonically. But when streaming replication is
13286+
restarted this will back off to the replication starting position,
13287+
typically the beginning of the WAL file containing the current
13288+
replay location. If recovery has completed this will remain static at
13289+
the value of the last WAL record received and synced to disk during
13290+
recovery. If streaming replication is disabled, or if it has not yet
13291+
started, the function returns NULL.
1328913292
</entry>
1329013293
</row>
1329113294
<row>

0 commit comments

Comments
 (0)