]> git.ipfire.org Git - thirdparty/postgresql.git/commitdiff
Add missing TidRangePath handling in print_path()
authorDavid Rowley <drowley@postgresql.org>
Thu, 28 Sep 2023 11:03:26 +0000 (00:03 +1300)
committerDavid Rowley <drowley@postgresql.org>
Thu, 28 Sep 2023 11:03:26 +0000 (00:03 +1300)
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

index 1a2396f623ceea6999d9ee6b8bc5d4bf8b413ff5..4e02439ce36dd2bc62c85028210874ee8b785c7b 100644 (file)
@@ -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;