Re: Proposal to use JSON for Postgres Parser format

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: Proposal to use JSON for Postgres Parser format
Дата
Msg-id CA+hUKG+iBrJX=Lug5_wJHoK1wfKgLKt=C1ttfrvQ1bOzNwjjLg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Proposal to use JSON for Postgres Parser format  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Proposal to use JSON for Postgres Parser format  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-hackers
On Tue, Sep 20, 2022 at 3:58 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > 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).
>
> Wow, where did you find a commit history for Berkeley's code?
> There's evidence in the tarballs I have that they were using
> RCS, but I never heard that the repo was made public.

One of the tarballs at https://dsf.berkeley.edu/postgres.html has the
complete RCS history, but Stas Kelvich imported it to github as Peter
G has just reported faster than I could.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Proposal to use JSON for Postgres Parser format
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Patch proposal: make use of regular expressions for the username in pg_hba.conf