| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Update InsertPgAttributeTuple comment to match new signature |
| Date: | 2020-06-22 14:27:18 |
| Message-ID: | 4E4E4B33-9FDF-4D21-B77A-642D027AEAD9@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The comment for InsertPgAttributeTuple no longer, since 911e702077037996, match
reality as attoptions isn't always initialized to NULL. The attached removes
mention of attoptions, and updates the list of always-NULL attributes to match
what the code does (the git history didn't provide rationale for why they were
omitted so it seemed like an oversight).
cheers ./daniel
| Attachment | Content-Type | Size |
|---|---|---|
| insertpgattributetuple_comment.patch | application/octet-stream | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-06-22 14:31:14 | Re: suggest to rename enable_incrementalsort |
| Previous Message | Robert Haas | 2020-06-22 14:20:02 | Re: Parallel Seq Scan vs kernel read ahead |