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:16 +0200 |
| commit | 5f0ba4abb33640205f38e5bee1e981da25175acf (patch) | |
| tree | ad5d2f969b01eec3d036570c00249efcead05f47 /src/backend/libpq/auth.c | |
| parent | f0241d648661c6650a32d26df2216ed78ba7953f (diff) | |
| download | postgresql-5f0ba4abb33640205f38e5bee1e981da25175acf.tar.gz postgresql-5f0ba4abb33640205f38e5bee1e981da25175acf.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/backend/libpq/auth.c')
0 files changed, 0 insertions, 0 deletions