]> granicus.if.org Git - postgresql/commitdiff
Remove false comment about speculative insertion.
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>
Mon, 27 Jul 2015 08:46:11 +0000 (11:46 +0300)
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>
Mon, 27 Jul 2015 08:46:11 +0000 (11:46 +0300)
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

src/backend/executor/nodeModifyTable.c

index 874ca6a69bcd24002f5cd9e27485fae296f0897c..1ef76d092859311abdc28afe7992e6783e25e72a 100644 (file)
@@ -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;