In [1] Andrey highlighted that I'd forgotten to add print_path()
handling for TidRangePaths in bb437f995.

I know the OPTIMIZER_DEBUG code isn't exactly well used.  I never
personally use it and I work quite a bit in the planner, however, if
we're keeping it, I thought maybe we might get the memo of missing
paths a bit sooner if we add an Assert(false) in the default cases.

Is the attached worthwhile?

David

[1] 
https://www.postgresql.org/message-id/379082d6-1b6a-4cd6-9ecf-7157d8c08...@postgrespro.ru

Attachment: assert_fail_unknown_paths_in_print_path.patch
Description: Binary data

Reply via email to