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:41 +0200 |
| commit | 38b38fb12244c640230b1fd71d2c55ecc04844fa (patch) | |
| tree | a05abf3060e08b95050440e25be14196cafc9e07 /src/backend/regex/regexec.c | |
| parent | 806e6d1ddb90fcbc3b59b17434cafeb4af51c126 (diff) | |
| download | postgresql-38b38fb12244c640230b1fd71d2c55ecc04844fa.tar.gz postgresql-38b38fb12244c640230b1fd71d2c55ecc04844fa.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/regex/regexec.c')
0 files changed, 0 insertions, 0 deletions