upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-03-01 04:40:42 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Report WAL flush, not insert, position in replication IDENTIFY_SYSTEM

Browse source 
When beginning streaming replication, the client usually issues the
IDENTIFY_SYSTEM command, which used to return the current WAL insert
position. That's not suitable for the intended purpose of that field,
however. pg_receivexlog uses it to start replication from the reported
point, but if it hasn't been flushed to disk yet, it will fail. Change
IDENTIFY_SYSTEM to report the flush position instead.

Backpatch to 9.1 and above. 9.0 doesn't report any WAL position.
This commit is contained in:
Heikki Linnakangas 2015-02-06 11:18:14 +02:00
parent eae798ae1d
commit 2af568c6b5
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/src/sgml/protocol.sgml
View file

@ -1338,7 +1338,7 @@ The commands accepted in walsender mode are:
</term>
<listitem>
<para>
Current xlog write location. Useful to get a known location in the
Current xlog flush location. Useful to get a known location in the
transaction log where streaming can start.
</para>
</listitem>

2
src/backend/replication/walsender.c
View file

@ -298,7 +298,7 @@ IdentifySystem(void)
GetSystemIdentifier());
snprintf(tli, sizeof(tli), "%u", ThisTimeLineID);
logptr = am_cascading_walsender ? GetStandbyFlushRecPtr(NULL) : GetInsertRecPtr();
logptr = am_cascading_walsender ? GetStandbyFlushRecPtr(NULL) : GetFlushRecPtr();
snprintf(xpos, sizeof(xpos), "%X/%X",
logptr.xlogid, logptr.xrecoff);