Missed TidRangePath in the print_path switch - Mailing list pgsql-bugs

From Andrey Lepikhov
Subject Missed TidRangePath in the print_path switch
Date
Msg-id 379082d6-1b6a-4cd6-9ecf-7157d8c08635@postgrespro.ru
Whole thread Raw
Responses Re: Missed TidRangePath in the print_path switch
List pgsql-bugs
Hi,

The TidRangePath node was introduced three years ago. However, path 
printing machinery still does not support it. It isn't enjoyable to add 
this string of code each time. I suggest adding it now.
Also, I propose not printing "???path" in the default case but throwing 
a warning - see the patch in the attachment. It can help to avoid such 
slip-ups next time.
It generally makes sense to generate such long switches automatically, 
likewise nodeToString.

-- 
regards,
Andrey Lepikhov
Postgres Professional
Attachment

pgsql-bugs by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index
Next
From: Andrey Lepikhov
Date:
Subject: Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery