From: Michael Paquier Date: Mon, 13 Jan 2020 08:57:38 +0000 (+0900) Subject: Fix comment in heapam.c X-Git-Tag: REL_13_BETA1~882 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7689d907bbb177fa2a8f5aca3f968761dd16bf28;p=thirdparty%2Fpostgresql.git Fix comment in heapam.c Improvement per suggestion from Tom Lane. Author: Daniel Gustafsson Discussion: https://postgr.es/m/FED18699-4270-4778-8DA8-10F119A5ECF3@yesql.se --- diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c index 7b8490d4e52..5ddb6e85e97 100644 --- a/src/backend/access/heap/heapam.c +++ b/src/backend/access/heap/heapam.c @@ -2145,7 +2145,7 @@ heap_multi_insert(Relation relation, TupleTableSlot **slots, int ntuples, * that check MUST be done at least past the point of acquiring an * exclusive buffer content lock on every buffer that will be affected, * and MAY be done after all inserts are reflected in the buffers and - * those locks are released; otherwise there race condition. Since + * those locks are released; otherwise there is a race condition. Since * multiple buffers can be locked and unlocked in the loop below, and it * would not be feasible to identify and lock all of those buffers before * the loop, we must do a final check at the end.