From: Michael Paquier <michael@paquier.xyz>
Date: Wed, 17 Mar 2021 09:07:00 +0000 (+0900)
Subject: Fix comment in indexing.c
X-Git-Tag: REL_14_BETA1~547
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9fd2952cf4920d563e9cea51634c5b364d57f71a;p=thirdparty%2Fpostgresql.git

Fix comment in indexing.c

578b229, that removed support for WITH OIDS, has changed
CatalogTupleInsert() to not return an Oid, but one comment was still
mentioning that.

Author: Vik Fearing
Discussion: https://postgr.es/m/fef01975-ed10-3601-7b9e-80ecef72d00b@postgresfriends.org
---

diff --git a/src/backend/catalog/indexing.c b/src/backend/catalog/indexing.c
index 284ceaa6b9c..4d1440cd3a9 100644
--- a/src/backend/catalog/indexing.c
+++ b/src/backend/catalog/indexing.c
@@ -210,7 +210,6 @@ CatalogTupleCheckConstraints(Relation heapRel, HeapTuple tup)
  * CatalogTupleInsert - do heap and indexing work for a new catalog tuple
  *
  * Insert the tuple data in "tup" into the specified catalog relation.
- * The Oid of the inserted tuple is returned.
  *
  * This is a convenience routine for the common case of inserting a single
  * tuple in a system catalog; it inserts a new heap tuple, keeping indexes