diff options
author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2015-02-06 11:18:14 +0200 |
---|---|---|
committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2015-02-06 11:27:12 +0200 |
commit | 3bc4c694271bfe28b909f43d45fe5168c18ad5b8 (patch) | |
tree | 4064144ae6f9a370ba228185a73fb4bee1e8eebf /src/tutorial/funcs.c | |
parent | 48a565d78ba9413317d6095010cf622e9d6a36eb (diff) | |
download | postgresql-3bc4c694271bfe28b909f43d45fe5168c18ad5b8.tar.gz postgresql-3bc4c694271bfe28b909f43d45fe5168c18ad5b8.zip |
Report WAL flush, not insert, position in replication IDENTIFY_SYSTEM
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.
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions