postgres.git / summary / log / commit / refs

commit    a0bfd65993948f5d299e37f33c658cdee79bb237
Author:   David Rowley <drowley@postgresql.org>
Date:     Thu Sep 28 11:03:26 2023 +0000
First released in: 17.0, 14.10, 15.5, 16.1

    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


 src/backend/optimizer/path/allpaths.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/backend/optimizer/path/allpaths.c b/src/backend/optimizer/path/allpaths.c
index 1a2396f623c..4e02439ce36 100644
--- a/src/backend/optimizer/path/allpaths.c
+++ b/src/backend/optimizer/path/allpaths.c
@@ -4447,6 +4447,9 @@ print_path(PlannerInfo *root, Path *path, int indent)
 		case T_TidPath:
 			ptype = "TidScan";
 			break;
+		case T_TidRangePath:
+			ptype = "TidRangePath";
+			break;
 		case T_SubqueryScanPath:
 			ptype = "SubqueryScan";
 			break;


[parent: 0db39e633812]