Re: Proposal to use JSON for Postgres Parser format

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal to use JSON for Postgres Parser format
Date: 2022-10-28 13:26:51
Message-ID: 40138e34-0415-b616-e6a7-84a274bc300e@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-10-28 13:27:46 Re: psql: Add command to use extended query protocol
Previous Message vignesh C 2022-10-28 12:04:37 Re: Improve tab completion for ALTER FUNCTION/PROCEDURE/ROUTINE