pgsql: Add missing TidRangePath handling in print_path() - Mailing list pgsql-committers

From David Rowley
Subject pgsql: Add missing TidRangePath handling in print_path()
Date
Msg-id E1qlooh-006S3V-QI@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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(+)


pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Add missing TidRangePath handling in print_path()
Next
From: Daniel Gustafsson
Date:
Subject: pgsql: doc: Clarify where ereport severity levels are defined