Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit a3554b2

Browse files
committed
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 911e702 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
1 parent 7ce4615 commit a3554b2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/catalog/heap.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -714,8 +714,8 @@ CheckAttributeType(const char *attname,
714714
* Construct and insert a new tuple in pg_attribute.
715715
*
716716
* Caller has already opened and locked pg_attribute. new_attribute is the
717-
* attribute to insert. attcacheoff is always initialized to -1, attacl and
718-
* attoptions are always initialized to NULL.
717+
* attribute to insert. attcacheoff is always initialized to -1, attacl,
718+
* attfdwoptions and attmissingval are always initialized to NULL.
719719
*
720720
* indstate is the index state for CatalogTupleInsertWithInfo. It can be
721721
* passed as NULL, in which case we'll fetch the necessary info. (Don't do

0 commit comments

Comments
 (0)