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
Date: Thu, 7 Nov 2024 02:23:44 +0100
Message-ID: <20241107022344.eb99b565ecbf01aed919e7cd@magnetkern.de> (raw)
In-Reply-To: <3305167.1730932202@sss.pgh.pa.us>
References: <18693-65968418890877b4@postgresql.org>
<3305167.1730932202@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: jbe-mlist@magnetkern.de, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type
In-Reply-To: <20241107022344.eb99b565ecbf01aed919e7cd@magnetkern.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox