pgsql: Remove EState.es_range_table_array.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Remove EState.es_range_table_array.
Date: 2019-08-12 15:58:42
Message-ID: E1hxCiY-0003bf-J0@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Remove EState.es_range_table_array.

Now that list_nth is O(1), there's no good reason to maintain a
separate array of RTE pointers rather than indexing into
estate->es_range_table. Deleting the array doesn't save all that
much either; but just on cleanliness grounds, it's better not to
have duplicate representations of the identical information.

Discussion: https://postgr.es/m/14960.1565384592@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3c926587b5928795e54dfea65c712a604f63cdeb

Modified Files
--------------
src/backend/executor/execMain.c | 1 -
src/backend/executor/execUtils.c | 23 +++++------------------
src/include/executor/executor.h | 3 +--
src/include/nodes/execnodes.h | 1 -
4 files changed, 6 insertions(+), 22 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-08-12 17:16:13 pgsql: Fix planner's test for case-foldable characters in ILIKE with IC
Previous Message Tom Lane 2019-08-12 15:20:27 pgsql: Rationalize use of list_concat + list_copy combinations.