Commit a3554b2d authored by Michael Paquier's avatar Michael Paquier

Fix comment in heap.c

The description of InsertPgAttributeTuple() does not match its handling
of pg_attribute contents with NULL values for a long time, with 911e7020
making things more inconsistent.  This adjusts the description to match
the reality.

Author: Daniel Gustafsson
Discussion: https://postgr.es/m/4E4E4B33-9FDF-4D21-B77A-642D027AEAD9@yesql.se
parent 7ce46156
...@@ -714,8 +714,8 @@ CheckAttributeType(const char *attname, ...@@ -714,8 +714,8 @@ CheckAttributeType(const char *attname,
* Construct and insert a new tuple in pg_attribute. * Construct and insert a new tuple in pg_attribute.
* *
* Caller has already opened and locked pg_attribute. new_attribute is the * Caller has already opened and locked pg_attribute. new_attribute is the
* attribute to insert. attcacheoff is always initialized to -1, attacl and * attribute to insert. attcacheoff is always initialized to -1, attacl,
* attoptions are always initialized to NULL. * attfdwoptions and attmissingval are always initialized to NULL.
* *
* indstate is the index state for CatalogTupleInsertWithInfo. It can be * indstate is the index state for CatalogTupleInsertWithInfo. It can be
* passed as NULL, in which case we'll fetch the necessary info. (Don't do * passed as NULL, in which case we'll fetch the necessary info. (Don't do
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment