aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-03-17 18:07:00 +0900
committerMichael Paquier <michael@paquier.xyz>2021-03-17 18:07:00 +0900
commit9fd2952cf4920d563e9cea51634c5b364d57f71a (patch)
tree033f3b6917ffe6af01fb204bfc67a9e17b68908f /src
parente1ae40f381d0582981b1e63856bd4b060cfe2d53 (diff)
downloadpostgresql-9fd2952cf4920d563e9cea51634c5b364d57f71a.tar.gz
postgresql-9fd2952cf4920d563e9cea51634c5b364d57f71a.zip
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
Diffstat (limited to 'src')
-rw-r--r--src/backend/catalog/indexing.c1
1 files changed, 0 insertions, 1 deletions
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