aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-01-15 12:07:10 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-01-15 12:07:10 -0500
commit1c53c4dec3985512f7f2f53c9d76a5295cd0a2dd (patch)
treed73a6f1954718d48d622162c98bfa6ca5ddc2422 /src/backend/executor/nodeModifyTable.c
parent0944ec54de389b4b8a471ca1f40f1b9d81de1f30 (diff)
downloadpostgresql-1c53c4dec3985512f7f2f53c9d76a5295cd0a2dd.tar.gz
postgresql-1c53c4dec3985512f7f2f53c9d76a5295cd0a2dd.zip
Finish reverting "recheck_on_update" patch.
This reverts commit c203d6cf8 and some follow-on fixes, completing the task begun in commit 5d28c9bd7. If that feature is ever resurrected, the code will look quite a bit different from this, so it seems best to start from a clean slate. The v11 branch is not touched; in that branch, the recheck_on_update storage option remains present, but nonfunctional and undocumented. Discussion: https://postgr.es/m/20190114223409.3tcvejfhlvbucrv5@alap3.anarazel.de
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions