diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2012-11-23 18:51:51 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2012-11-23 19:14:54 +0200 |
| commit | 3f7b04d6f694b447c17999ef0aed406e658de82f (patch) | |
| tree | 2fbab17c6a3dc9a1269cdc30cadea6be19afa4d0 /src/backend/executor/nodeModifyTable.c | |
| parent | 430b47f382609c567bd87ff28a81ea5055d173d5 (diff) | |
| download | postgresql-3f7b04d6f694b447c17999ef0aed406e658de82f.tar.gz postgresql-3f7b04d6f694b447c17999ef0aed406e658de82f.zip | |
pg_stat_replication.sync_state was displayed incorrectly at page boundary.
XLogRecPtrIsInvalid() only checks the xrecoff field, which is correct when
checking if a WAL record could legally begin at the given position, but WAL
sending can legally be paused at a page boundary, in which case xrecoff is
0. Use XLByteEQ(..., InvalidXLogRecPtr) instead, which checks that both
xlogid and xrecoff are 0.
9.3 doesn't have this problem because XLogRecPtr is now a single 64-bit
integer, so XLogRecPtrIsInvalid() does the right thing. Apply to 9.2, and
9.1 where pg_stat_replication view was introduced.
Kyotaro HORIGUCHI, reviewed by Fujii Masao.
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions