From: David Rowley <drowley@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Add missing TidRangePath handling in print_path()
Date: Thu, 28 Sep 2023 11:04:23 +0000
Message-ID: <E1qlooh-006S3V-QI@gemulon.postgresql.org> (raw)
Add missing TidRangePath handling in print_path()
Tid Range scans were added back in bb437f995. That commit forgot to add
handling for TidRangePaths in print_path().
Only people building with OPTIMIZER_DEBUG might have noticed this, which
likely is the reason it's taken 4 years for anyone to notice.
Author: Andrey Lepikhov
Reported-by: Andrey Lepikhov
Discussion: https://postgr.es/m/379082d6-1b6a-4cd6-9ecf-7157d8c08635@postgrespro.ru
Backpatch-through: 14, where bb437f995 was introduced
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/9861fe2cdd0216f6e25377cab3b95fccd854de84
Modified Files
--------------
src/backend/optimizer/path/allpaths.c | 3 +++
1 file changed, 3 insertions(+)
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: drowley@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add missing TidRangePath handling in print_path()
In-Reply-To: <E1qlooh-006S3V-QI@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