| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fixes a trivial bug in dumped parse/query/plan trees |
| Date: | 2025-08-25 08:57:09 |
| Message-ID: | 39F7E407-4250-4810-A98F-DD25FA3EBCBB@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Aug 25, 2025, at 16:02, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>
> What about external parsers written for this format which might now break?
> (Judging by the commitlog I believe this format is intentional and not a bug.)
>
>
The commit message says:
Let's adopt a format similar to that used for Lists, that is "<>"
for a NULL pointer or "(item item item)" otherwise. Also retool
the code to not have so many copies of the identical logic.
It mentioned “(item item item)”, not a whitespace in front of the first item.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-08-25 09:10:42 | Calling PGReserveSemaphores() from CreateOrAttachShmemStructs |
| Previous Message | Alyona Vinter | 2025-08-25 08:31:35 | Re: Making WAL archiving faster — multi-file support and async ideas |