From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
cc: Amit Langote <amitlangote09@gmail.com>,
        Alvaro Herrera <alvherre@alvh.no-ip.org>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: pgsql: Add more SQL/JSON constructor functions
In-reply-to: <65d2544e-4a11-448d-9683-7bce0d43565d@eisentraut.org>
References: <202405271313.qkl63gffldmx@alvherre.pgsql> <202405271326.5a5rprki64aw@alvherre.pgsql> <CA+HiwqE+y_HmGJpKk2_w+CUzmAw=Z5zd6j3_LmCPiGpFyN1gzQ@mail.gmail.com> <3189.1717001075@sss.pgh.pa.us> <50a780ab-f1a4-4c5f-b9a1-88a174cf12af@eisentraut.org> <2416639.1717389996@sss.pgh.pa.us> <65d2544e-4a11-448d-9683-7bce0d43565d@eisentraut.org>
Comments: In-reply-to Peter Eisentraut <peter@eisentraut.org>
	message dated "Mon, 03 Jun 2024 11:15:37 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <75663.1717435222.1@sss.pgh.pa.us>
Date: Mon, 03 Jun 2024 13:20:22 -0400
Message-ID: <75664.1717435222@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/75664.1717435222%40sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter@eisentraut.org> writes:
> On 02.06.24 21:46, Tom Lane wrote:
>> If you don't
>> like our current behavior, then either you have to say that RETURNING
>> with a length-limited target type is illegal (which is problematic
>> for the spec, since they have no such type) or that the cast behaves
>> like an implicit cast, with errors for overlength input (which I find
>> to be an unintuitive definition for a construct that names the target
>> type explicitly).

> It asks for the latter behavior, essentially (but it's not defined in 
> terms of casts).  It says:

Meh.  Who needs consistency?  But I guess the answer is to do what was
suggested earlier and change the code to use COERCE_IMPLICIT_CAST.

			regards, tom lane