From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
cc: Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>,
        "Jonathan S. Katz" <jkatz@postgresql.org>,
        Nikita Glukhov <n.gluhov@postgrespro.ru>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
        Andrew Dunstan <andrew@dunslane.net>,
        Michael Paquier <michael@paquier.xyz>,
        John Naylor <john.naylor@enterprisedb.com>,
        Amit Langote <amitlangote09@gmail.com>
Subject: Re: SQL/JSON features for v15
In-reply-to: 
 <CAFj8pRDyv7vsSmN8RcpugOCctM-UudV58z14pyvJz2ZtwXPCpg@mail.gmail.com>
References: <20220815223853.itrlpqgpqheg6r6a@awork3.anarazel.de>
 <225d341b-f310-eed0-ceff-b8ec61669d9f@postgrespro.ru>
 <20220816021425.5sa6gx67zmpou3bc@awork3.anarazel.de>
 <8d0ffc54-469a-ffab-68a3-8b547e24a08d@postgresql.org>
 <7d83684b-7932-9f29-400b-0beedfafcdd4@postgrespro.ru>
 <69022273-e7e3-6d1a-10f8-d1b4740e4b97@postgresql.org>
 <92cab50c-152b-84fc-fd49-12b936113a3d@postgresql.org>
 <CA+TgmoaAZq6rRdVA65PBXBKs=jUHhf42Jf78kBLOaX3c6J7MfQ@mail.gmail.com>
 <20220823155511.ffyntlyjl6wrgljv@awork3.anarazel.de>
 <CAFj8pRBqhLvTvf8_zHoM6Jc656atEWRUPnp6i_T5hjExeB83Ag@mail.gmail.com>
 <20220823172718.o4p25k2bcrmsnj3a@awork3.anarazel.de>
 <CAFj8pRDyv7vsSmN8RcpugOCctM-UudV58z14pyvJz2ZtwXPCpg@mail.gmail.com>
Comments: In-reply-to Pavel Stehule <pavel.stehule@gmail.com>
	message dated "Tue, 23 Aug 2022 19:38:35 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <726611.1661276738.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Aug 2022 13:45:38 -0400
Message-ID: <726612.1661276738@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/726612.1661276738%40sss.pgh.pa.us>
Precedence: bulk

Pavel Stehule <pavel.stehule@gmail.com> writes:
> =C3=BAt 23. 8. 2022 v 19:27 odes=C3=ADlatel Andres Freund <andres@anaraz=
el.de> napsal:
>> I think that's not true unfortunately. You can specify return types, an=
d
>> composite types can be populated. Which essentially requires arbitrary
>> coercions.

> Please, can you send an example? Maybe we try to fix a feature that is n=
ot
> required by standard.

Even if it is required by spec, I'd have zero hesitation about tossing
that case overboard if that's what we need to do to get to a shippable
feature.

			regards, tom lane