From b2a177bff10e86016a53bb7f06f7d5e63649e27d Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Mon, 5 Mar 2018 15:28:03 -0800 Subject: [PATCH] Fix HEAP_INSERT_IS_SPECULATIVE to HEAP_INSERT_SPECULATIVE in comments. This was wrong since 168d5805e4c08bed7b95d351bf097cff7c07dd65, which introduced speculative inserts. Author: Andres Freund --- src/backend/access/heap/heapam.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 302f8c63ad..c08ab14c02 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -2411,7 +2411,7 @@ ReleaseBulkInsertStatePin(BulkInsertState bistate) * This causes rows to be frozen, which is an MVCC violation and * requires explicit options chosen by user. * - * HEAP_INSERT_IS_SPECULATIVE is used on so-called "speculative insertions", + * HEAP_INSERT_SPECULATIVE is used on so-called "speculative insertions", * which can be backed out afterwards without aborting the whole transaction. * Other sessions can wait for the speculative insertion to be confirmed, * turning it into a regular tuple, or aborted, as if it never existed. @@ -2420,8 +2420,8 @@ ReleaseBulkInsertStatePin(BulkInsertState bistate) * * Note that most of these options will be applied when inserting into the * heap's TOAST table, too, if the tuple requires any out-of-line data. Only - * HEAP_INSERT_IS_SPECULATIVE is explicitly ignored, as the toast data does - * not partake in speculative insertion. + * HEAP_INSERT_SPECULATIVE is explicitly ignored, as the toast data does not + * partake in speculative insertion. * * The BulkInsertState object (if any; bistate can be NULL for default * behavior) is also just passed through to RelationGetBufferForTuple. -- 2.40.0