From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: Jacob Champion <pchampion@vmware.com>,
 "daniel@yesql.se" <daniel@yesql.se>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: [PATCH] Make jsonapi usable from libpq
In-reply-to: <YOU9TnKe8Pt7V1pn@paquier.xyz>
References: <a250d475ba1c0cc0efb7dfec8e538fcc77cdcb8e.camel@vmware.com>
 <YNQedHwheUaTnnGt@paquier.xyz>
 <daeb22ec6ca8ef61e94d766a9b35fb03cabed38e.camel@vmware.com>
 <YNZ2mnsbDVJQrA/a@paquier.xyz>
 <c475057da66fdc5ae707a89f5b44dd8508b86f7e.camel@vmware.com>
 <497374.1624992620@sss.pgh.pa.us>
 <ea0cdb0974cca85805c6d8131e8eeba0fd811444.camel@vmware.com>
 <499672.1624995269@sss.pgh.pa.us> <YOU9TnKe8Pt7V1pn@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Wed, 07 Jul 2021 14:36:14 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1805879.1625636520.1@sss.pgh.pa.us>
Date: Wed, 07 Jul 2021 01:42:00 -0400
Message-ID: <1805880.1625636520@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1805880.1625636520%40sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> It seems to me that this does not address yet the problems with the
> palloc/pstrdup in jsonapi.c though, which would need to rely on
> malloc() if we finish to use this code in libpq.  I am not sure yet
> that we have any need to do that yet as we may finish by not using
> OAUTH as SASL mechanism at the end in core.  So perhaps it would be
> better to just give up on this thread for now?

Yeah, I think there's nothing to do here unless we decide that we
have to have JSON-parsing ability inside libpq ... which is a
situation I think we should try hard to avoid.

			regards, tom lane