| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Missed TidRangePath in the print_path switch |
| Date: | 2023-09-28 05:07:48 |
| Message-ID: | 379082d6-1b6a-4cd6-9ecf-7157d8c08635@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| tidrangepath.patch | text/plain | 750 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Lepikhov | 2023-09-28 06:32:25 | Re: EXPLAIN Verbose issue - custom_scan_tlist can directly refer CTE and Subquery |
| Previous Message | Alexander Lakhin | 2023-09-28 05:00:00 | Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index |