From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal to use JSON for Postgres Parser format |
Date: | 2022-09-20 03:36:57 |
Message-ID: | CA+hUKG+z3K4qhRSq4bNSZ6STEwww3kJnfa5Zn2va=A_43x+5AA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 20, 2022 at 12:16 PM Michel Pelletier
<pelletier(dot)michel(at)gmail(dot)com> wrote:
> This non-standard format
FWIW, it derives from Lisp s-expressions, but deviates from Lisp's
default reader/printer behaviour in small ways, including being case
sensitive and using {NAME :x 1 ...} instead of #S(NAME :x 1 ...) for
structs for reasons that are lost AFAIK (there's a dark age between
the commit history of the old Berkeley repo and our current repo, and
it looks like plan nodes were still printed as #(NAME ...) at
Berkeley). At some point it was probably exchanging data between the
Lisp and C parts of POSTGRES, and you could maybe sorta claim it's
based on an ANSI standard (Lisp!), but not with a straight face :-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-09-20 03:39:49 | Re: Proposal to use JSON for Postgres Parser format |
Previous Message | Nathan Bossart | 2022-09-20 03:32:38 | Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures |