Union-ifying RangeTblEntry

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Union-ifying RangeTblEntry
Date: 2014-01-28 06:18:04
Message-ID: 52E74B9C.6010107@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 because the 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-01-28 06:33:54 Re: [COMMITTERS] pgsql: Keep pg_stat_statements' query texts in a file, not in shared me
Previous Message Rajeev rastogi 2014-01-28 06:17:25 Re: Add min and max execute statement time in pg_stat_statement