Re: BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type

From: Jan Behrens <jbe-mlist(at)magnetkern(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18693: Column names not set when using SELECT STRICT INTO with RECORD type
Date: 2024-11-07 01:23:44
Message-ID: 20241107022344.eb99b565ecbf01aed919e7cd@magnetkern.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 06 Nov 2024 17:30:02 -0500
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tender Wang 2024-11-07 06:47:42 Re: BUG #18692: Segmentation fault when extending a varchar column with a gist index with custom signal length
Previous Message Thomas Munro 2024-11-07 00:01:58 Re: Detection of hadware feature => please do not use signal