summaryrefslogtreecommitdiff
path: root/contrib/jsonb_plperl/jsonb_plperl.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-07-09 19:26:19 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2018-07-09 19:26:19 -0400
commit0905fe8911ea06df17a3ba3f086e98ca5c7b560c (patch)
treee8cb0d2f060f0e74e721a1d5091cb37aa5312c28 /contrib/jsonb_plperl/jsonb_plperl.c
parenta22445ff0be2e4a008b2dd1aaa963f8f7c70cab9 (diff)
downloadpostgresql-0905fe8911ea06df17a3ba3f086e98ca5c7b560c.tar.gz
Avoid emitting a bogus WAL record when recycling an all-zero btree page.
Commit fafa374f2 caused _bt_getbuf() to possibly emit a WAL record for a page that it was about to recycle. However, it failed to distinguish all-zero pages from dead pages, which is important because only the latter have valid btpo.xact values, or indeed any special space at all. Recycling an all-zero page with XLogStandbyInfoActive() enabled therefore led to an Assert failure, or to emission of a WAL record containing a bogus cutoff XID, which might lead to unnecessary query cancellations on hot standby servers. Per reports from Antonin Houska and 自己. Amit Kapila was first to propose this fix, and Robert Haas, myself, and Kyotaro Horiguchi reviewed it at various times. This is an old bug, so back-patch to all supported branches. Discussion: https://postgr.es/m/2628.1474272158@localhost Discussion: https://postgr.es/m/48875502.f4a0.1635f0c27b0.Coremail.zoulx1982@163.com
Diffstat (limited to 'contrib/jsonb_plperl/jsonb_plperl.c')
0 files changed, 0 insertions, 0 deletions