Re: RangeTblEntry.inh vs. RTE_SUBQUERY - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: RangeTblEntry.inh vs. RTE_SUBQUERY
Date
Msg-id 202402291907.e6ax6kfnktt4@alvherre.pgsql
Whole thread Raw
In response to Re: RangeTblEntry.inh vs. RTE_SUBQUERY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: RangeTblEntry.inh vs. RTE_SUBQUERY
List pgsql-hackers
On 2024-Feb-29, Tom Lane wrote:

> I agree that perminfoindex seems to have suffered from add-at-the-end
> syndrome, and if we do touch the field order you made an improvement
> there.  (BTW, who thought they needn't bother with a comment for
> perminfoindex?)

There is a comment for it, or at least a61b1f74823c added one, though
not immediately adjacent.  I do see that it's now further away than it
was.  Perhaps we could add /* index of RTEPermissionInfo entry, or 0 */
to the line.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"The ability of users to misuse tools is, of course, legendary" (David Steele)
https://postgr.es/m/11b38a96-6ded-4668-b772-40f992132797@pgmasters.net



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Comments on Custom RMGRs
Next
From: Phil Florent
Date:
Subject: RE: Remove AIX Support (was: Re: Relation bulk write facility)