pgsql: Track scan reversals in MergeJoin - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Track scan reversals in MergeJoin
Date
Msg-id E1t0LsE-000ngC-4Z@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Track scan reversals in MergeJoin

The MergeJoin struct was tracking "mergeStrategies", which were an
array of btree strategy numbers, purely for the purpose of comparing
it later against btree strategies to determine if the scan direction
was forward or reverse.  Change that.  Instead, track
"mergeReversals", an array of bool, to indicate the same without an
unfortunate assumption that a strategy number refers specifically to a
btree strategy.

Author: Mark Dilger <mark.dilger@enterprisedb.com>
Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330@enterprisedb.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/c594f1ad2ba7cbe66e8ae98da4ffed06491d1082

Modified Files
--------------
src/backend/executor/nodeMergejoin.c    | 13 ++++---------
src/backend/optimizer/plan/createplan.c | 14 +++++++-------
src/include/nodes/plannodes.h           |  2 +-
3 files changed, 12 insertions(+), 17 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Run pgperltidy on newly-added test code
Next
From: Masahiko Sawada
Date:
Subject: pgsql: Use construct_array_builtin for FLOAT8OID instead of construct_a