Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit c4a1933

Browse filesBrowse files
committed
Add missing TidRangePath handling in print_path()
Tid Range scans were added back in bb437f9. 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 bb437f9 was introduced
1 parent c68f785 commit c4a1933
Copy full SHA for c4a1933

File tree

Expand file treeCollapse file tree

1 file changed

+3
-0
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+3
-0
lines changed

‎src/backend/optimizer/path/allpaths.c

Copy file name to clipboardExpand all lines: src/backend/optimizer/path/allpaths.c
+3Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4470,6 +4470,9 @@ print_path(PlannerInfo *root, Path *path, int indent)
44704470
case T_TidPath:
44714471
ptype = "TidScan";
44724472
break;
4473+
case T_TidRangePath:
4474+
ptype = "TidRangePath";
4475+
break;
44734476
case T_SubqueryScanPath:
44744477
ptype = "SubqueryScan";
44754478
break;

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.