pgsql: Remove EState.es_range_table_array. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Remove EState.es_range_table_array.
Date
Msg-id E1hxCiY-0003bf-J0@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Rationalize use of list_concat + list_copy combinations.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix planner's test for case-foldable characters in ILIKE withIC