summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorAlvaro Herrera2021-02-23 20:30:21 +0000
committerAlvaro Herrera2021-02-23 20:30:21 +0000
commit8deb6b38dc4c7a7fd4719ee45e4b00d62b27dffe (patch)
tree5f3f90dd0620287eb900edd64cec34b5c0e0fbd4 /src/backend/access/gist/gistxlog.c
parent3db05e76f92846d4b54d7de251b0875cf1e23aa4 (diff)
Reinstate HEAP_XMAX_LOCK_ONLY|HEAP_KEYS_UPDATED as allowed
Commit 866e24d47db1 added an assert that HEAP_XMAX_LOCK_ONLY and HEAP_KEYS_UPDATED cannot appear together, on the faulty assumption that the latter necessarily referred to an update and not a tuple lock; but that's wrong, because SELECT FOR UPDATE can use precisely that combination, as evidenced by the amcheck test case added here. Remove the Assert(), and also patch amcheck's verify_heapam.c to not complain if the combination is found. Also, out of overabundance of caution, update (across all branches) README.tuplock to be more explicit about this. Author: Julien Rouhaud <[email protected]> Reviewed-by: Mahendra Singh Thalor <[email protected]> Reviewed-by: Dilip Kumar <[email protected]> Discussion: https://postgr.es/m/20210124061758.GA11756@nol
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions