| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RelationGetIndexAttrBitmap comment outdated |
| Date: | 2023-07-12 14:37:16 |
| Message-ID: | 20230712143716.cvrkdktgwwvuwjrr@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I realized that commit 19d8e2308bc5 (and 5753d4ee320b before that) added
a new output type to RelationGetIndexAttrBitmap but forgot to list its
effect in the function's documenting comment. Here's a patch that
updates it, making it more specific (and IMO more readable). I also add
a comment to the enum definition, to remind people that the other one
needs to be modified.
This ought to be backpatched to 16.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"La conclusión que podemos sacar de esos estudios es que
no podemos sacar ninguna conclusión de ellos" (Tanenbaum)
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-document-RelationGetIndexAttrBitmap.patch | text/x-diff | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-07-12 14:42:48 | Re: RelationGetIndexAttrBitmap comment outdated |
| Previous Message | Tristan Partin | 2023-07-12 14:35:58 | Re: Clean up some signal usage mainly related to Windows |