aboutsummaryrefslogtreecommitdiff
path: root/contrib/jsonb_plperl/jsonb_plperl.control
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-02-09 12:02:57 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-02-09 12:02:57 -0500
commit4093ff573702e9f157507340593680dc2c75e88e (patch)
tree0cea589bd192e3f5b3130578d85cee4ceb068026 /contrib/jsonb_plperl/jsonb_plperl.control
parent55173d2e663fbe32430665ce7bd65a47856dc237 (diff)
downloadpostgresql-4093ff573702e9f157507340593680dc2c75e88e.tar.gz
postgresql-4093ff573702e9f157507340593680dc2c75e88e.zip
Store the deletion horizon XID for a deleted GIN page on the right page.
Commit b10714080 moved the GinPageSetDeleteXid() call to a spot where the "page" variable was pointing to the wrong page, causing the XID to be inserted on a page that's not being deleted, thus allowing later GinPageIsRecyclable tests to recycle the deleted page too soon. It might be a good idea to stop using the single "page" variable for multiple purposes in this function. But for the moment I just moved the GinPageSetDeleteXid() call down beside the GinPageSetDeleted() call, which seems like a more logical place for it anyway. Back-patch to v11, as the faulty patch was. (Fortunately, the bug hasn't made it into any release yet.) Discussion: https://postgr.es/m/21620.1581098806@sss.pgh.pa.us
Diffstat (limited to 'contrib/jsonb_plperl/jsonb_plperl.control')
0 files changed, 0 insertions, 0 deletions