From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Track scan reversals in MergeJoin
Date: Mon, 14 Oct 2024 14:16:37 +0000
Message-ID: <E1t0LsE-000ngC-4Z@gemulon.postgresql.org> (raw)
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(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: peter@eisentraut.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Track scan reversals in MergeJoin
In-Reply-To: <E1t0LsE-000ngC-4Z@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox