pgsql: Track scan reversals in MergeJoin

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Track scan reversals in MergeJoin
Date: 2024-10-14 14:16:37
Message-ID: E1t0LsE-000ngC-4Z@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)dilger(at)enterprisedb(dot)com>
Discussion: https://www.postgresql.org/message-id/flat/E72EAA49-354D-4C2E-8EB9-255197F55330(at)enterprisedb(dot)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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2024-10-14 16:50:54 pgsql: Use construct_array_builtin for FLOAT8OID instead of construct_a
Previous Message Peter Eisentraut 2024-10-14 09:25:19 pgsql: Run pgperltidy on newly-added test code