Union-ifying RangeTblEntry - Mailing list pgsql-hackers

From Craig Ringer
Subject Union-ifying RangeTblEntry
Date
Msg-id 52E74B9C.6010107@2ndquadrant.com
Whole thread Raw
Responses Re: Union-ifying RangeTblEntry  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi all

I'm about to have to add _another_ flag to RangeTblEntry, to track
row-security expansion.

In the process I noticed the comment:
   /*    * XXX the fields applicable to only some rte kinds should be    * merged into a union.  I didn't do this yet
becausethe diffs    * would impact a lot of code that is being actively worked on.    * FIXME someday.    */
 

and it struck me that the end of the 9.4 commitfest might be a
reasonable time to do this now that PstgreSQL is subject to "pulsed"
development with commitfests.

As part of that, a number of the flag fields on RangeTblEntry into a
bitfield.

Comments?

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Rajeev rastogi
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Peter Geoghegan
Date:
Subject: Re: [COMMITTERS] pgsql: Keep pg_stat_statements' query texts in a file, not in shared me