Date: Thu, 7 Nov 2024 02:23:44 +0100
From: Jan Behrens <jbe-mlist@magnetkern.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18693: Column names not set when using SELECT STRICT INTO
 with RECORD type
Message-Id: <20241107022344.eb99b565ecbf01aed919e7cd@magnetkern.de>
In-Reply-To: <3305167.1730932202@sss.pgh.pa.us>
References: <18693-65968418890877b4@postgresql.org>
	<3305167.1730932202@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/20241107022344.eb99b565ecbf01aed919e7cd%40magnetkern.de>
Precedence: bulk

On Wed, 06 Nov 2024 17:30:02 -0500
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> PG Bug reporting form <noreply@postgresql.org> writes:
> [...]
> 
> You have the syntax wrong: what you intended (I presume) is
> 
>      SELECT a, b INTO STRICT r FROM (SELECT 'A' AS a, 'B' AS b) AS q;
> 
> With what you wrote, the STRICT is taken as an output column alias of
> the outer SELECT, [...]
> 
> 			regards, tom lane

Oooops, my apologies! It totally makes sense now.
Thanks for your thorough/helpful response.

Regards
Jan Behrens