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:32:37 +0200 |
| commit | 2af568c6b50293bedb10d4ebb8dca9fe13f435c5 (patch) | |
| tree | 6de25d98d69ff21894beb4ea11d47e048fe9967a /src/backend/optimizer/geqo/geqo_eval.c | |
| parent | eae798ae1d98f8f62cc0b93a2c6972985f070446 (diff) | |
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/backend/optimizer/geqo/geqo_eval.c')
0 files changed, 0 insertions, 0 deletions