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

From Alexander Korotkov
Subject Re: Proposal to use JSON for Postgres Parser format
Date
Msg-id CAPpHfduCg-oRjYQr4jhwtXgvPiLOpqRG7bmXOTkGZb0e52LUEQ@mail.gmail.com
Whole thread Raw
In response to Re: Proposal to use JSON for Postgres Parser format  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Proposal to use JSON for Postgres Parser format  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
List pgsql-hackers
On Fri, Oct 28, 2022 at 4:27 PM Andrew Dunstan <andrew@dunslane.net> wrote:
> On 2022-10-27 Th 19:38, Andres Freund wrote:
> > Hi,
> >
> > On 2022-09-19 22:29:15 -0400, Tom Lane wrote:
> >> Maybe a compromise could be found whereby we provide a conversion function
> >> that converts whatever the catalog storage format is to some JSON
> >> equivalent.  That would address the needs of external code that doesn't want
> >> to write a custom parser, while not tying us directly to JSON.
> > +1
> >
>
>
> Agreed.

+1

Michel, it seems that you now have a green light to implement node to
json function.

------
Regards,
Alexander Korotkov



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Code checks for App Devs, using new options for transaction behavior
Next
From: Aleksander Alekseev
Date:
Subject: Re: ResourceOwner refactoring