Re: Proposal to use JSON for Postgres Parser format - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Proposal to use JSON for Postgres Parser format
Date
Msg-id CA+hUKG+z3K4qhRSq4bNSZ6STEwww3kJnfa5Zn2va=A_43x+5AA@mail.gmail.com
Whole thread Raw
In response to Proposal to use JSON for Postgres Parser format  (Michel Pelletier <pelletier.michel@gmail.com>)
Responses Re: Proposal to use JSON for Postgres Parser format
List pgsql-hackers
On Tue, Sep 20, 2022 at 12:16 PM Michel Pelletier
<pelletier.michel@gmail.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 :-)



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures
Next
From: Tom Lane
Date:
Subject: Re: Proposal to use JSON for Postgres Parser format