From: Peter Geoghegan <pg@bowt.ie>
Date: Thu, 19 Mar 2020 21:56:56 +0000 (-0700)
Subject: nbtree: Remove obsolete _bt_pgaddtup() comments.
X-Git-Tag: REL_13_BETA1~508
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b27e1b3418b189e1a5aee13cbd09bff94f010a86;p=thirdparty%2Fpostgresql.git

nbtree: Remove obsolete _bt_pgaddtup() comments.

Remove comments that are a throw back to a time when nbtree cared about
write-ordering dependencies.  The comments are similar to those removed
by commit 9ee7414e, among others.
---

diff --git a/src/backend/access/nbtree/nbtinsert.c b/src/backend/access/nbtree/nbtinsert.c
index 2c3656c1cd3..00df0e1b88f 100644
--- a/src/backend/access/nbtree/nbtinsert.c
+++ b/src/backend/access/nbtree/nbtinsert.c
@@ -2531,11 +2531,6 @@ _bt_newroot(Relation rel, Buffer lbuf, Buffer rbuf)
 /*
  *	_bt_pgaddtup() -- add a data item to a particular page during split.
  *
- *		This routine adds the tuple to the page as requested.  It does
- *		not affect pin/lock status, but you'd better have a write lock
- *		and pin on the target buffer!  Don't forget to write and release
- *		the buffer afterwards, either.
- *
  *		The difference between this routine and a bare PageAddItem call is
  *		that this code knows that the leftmost data item on an internal
  *		btree page has a key that must be treated as minus infinity.