Message-ID: <0102019737692b90-b251a7ea-b3c5-4477-afff-5986a149580a-000000@eu-west-1.amazonses.com>
Date: Tue, 3 Jun 2025 20:08:48 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Combining scalar and row types in RETURNING
To: Adrian Klaver <adrian.klaver@aklaver.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: 'PostgreSQL' <pgsql-general@postgresql.org>
References: <01020197369aac89-01a7b7b4-b775-471e-ac8e-de8b28d87008-000000@eu-west-1.amazonses.com>
 <858949.1748969638@sss.pgh.pa.us>
 <01020197370480a4-f9b53911-e5a8-4bdb-81e5-de41d5db4d8c-000000@eu-west-1.amazonses.com>
 <228703a6-f1bf-4af8-a5d6-4edb5bcaa8cf@aklaver.com>
Content-Language: en-GB, de-DE
From: Ray O'Donnell <ray@rodonnell.ie>
In-Reply-To: <228703a6-f1bf-4af8-a5d6-4edb5bcaa8cf@aklaver.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Feedback-ID: ::1.eu-west-1.Bw1eu/7Uepg3xcsiFBL71JJRCh2A2yTFrgBhhiulXmU=:AmazonSES
Archived-At: <https://www.postgresql.org/message-id/0102019737692b90-b251a7ea-b3c5-4477-afff-5986a149580a-000000%40eu-west-1.amazonses.com>
Precedence: bulk

On 03/06/2025 20:01, Adrian Klaver wrote:
> On 6/3/25 11:18, Ray O'Donnell wrote:
>> On 03/06/2025 17:53, Tom Lane wrote:
>
>> Thanks a million for the explanation, Tom - that makes sense. I tried 
>> what you suggested, with mixed results:
>>
>> (i) Running the MERGE as a stand-alone query, with just RETURNING... 
>> , worked - I got a scalar and a row as expected.
>>
>> (ii) Running it in a function (actually a DO block), with m_new 
>> correctly declared as the table type, failed with the same error as 
>> before.
>>
>> (iii) Running (ii) but with the order of the items in RETURNING 
>> reversed -
>>
>>      ... returning t, merge_action() into m_new, m_action
>>
>> - gave me a different error:
>>
>> ERROR:  record variable cannot be part of multiple-item INTO list
>> LINE 53:         m, merge_action() into m_new, m_action
>>
>> ...which seems to answer my question definitively.
>
> This:
>
> ... returning t, merge_action() into m_new, m_action
>
> does not match this:
>
> LINE 53:         m, merge_action() into m_new, m_action
>
>
> Is this a copy and paste error or two different invocations of the 
> function?

Whoops, sorry, yes, that's a copy-and-paste error - the target table is 
aliased as "m" in my original.

Ray.


-- 
Raymond O'Donnell // Galway // Ireland
ray@rodonnell.ie