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+6_DkxZMo1ykRuYMk=r3iaaMy1szg46duJyhnNfu-OUA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal to use JSON for Postgres Parser format  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Tue, Sep 20, 2022 at 4:16 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> To explain my earlier guess: reader code for #S(STRUCTNAME ...) can
> bee seen here, though it's being lexed as "PLAN_SYM" so perhaps the
> author of that C already didn't know that was a general syntax for
> Lisp structs.  (Example: at a Lisp prompt, if you write (defstruct foo
> x y z) then (make-foo :x 1 :y 2 :z 3), the resulting object will be
> printed as #S(FOO :x 1 :y 2 :z 3), so I'm guessing that the POSTGRES
> Lisp code, which sadly (for me) was ripped out before even that repo
> IIUC, must have used defstruct-based plans.)

That defstruct guess is confirmed by page 36 and nearby of
https://dsf.berkeley.edu/papers/UCB-MS-zfong.pdf.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Lowering the default wal_blocksize to 4K
Next
From: Andres Freund
Date:
Subject: Re: New WAL record to detect the checkpoint redo location