aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2015-07-27 11:46:11 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2015-07-27 11:46:33 +0300
commitdd20a97219b569b92bdcbd0c195c214340298b4a (patch)
tree96b8b3361877e8bfea6d8ca1a0a64c8f58a18da9 /src/backend/executor/nodeModifyTable.c
parent8fb61e0b5430b8dada0eca18b99e3956f4eaf6cd (diff)
downloadpostgresql-dd20a97219b569b92bdcbd0c195c214340298b4a.tar.gz
postgresql-dd20a97219b569b92bdcbd0c195c214340298b4a.zip
Remove false comment about speculative insertion.
There is no full discussion of speculative insertions in the executor README. There is a high-level explanation in execIndexing.c, but it doesn't seem necessary to refer it from here. Peter Geoghegan
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
-rw-r--r--src/backend/executor/nodeModifyTable.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/backend/executor/nodeModifyTable.c b/src/backend/executor/nodeModifyTable.c
index 874ca6a69bc..1ef76d09285 100644
--- a/src/backend/executor/nodeModifyTable.c
+++ b/src/backend/executor/nodeModifyTable.c
@@ -351,8 +351,7 @@ ExecInsert(ModifyTableState *mtstate,
*
* We loop back here if we find a conflict below, either during
* the pre-check, or when we re-check after inserting the tuple
- * speculatively. See the executor README for a full discussion
- * of speculative insertion.
+ * speculatively.
*/
vlock:
specConflict = false;