Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ? - Mailing list pgsql-bugs

From Tobias Gierke
Subject Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
Date
Msg-id 81bf6542-4a06-9abc-a0d3-a95bc0da2200@code-sourcery.de
Whole thread Raw
In response to Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
Thanks for the hint & sorry for the noise, it's working now !

On Tue, Jan 26, 2021 at 5:56 AM Tobias Gierke <tobias.gierke@code-sourcery.de> wrote:
voip$#         SELECT (t1.a_major, t1.a_minor )::version_num INTO _myid

Bug or feature ?


Feature.  The first column of the select result gets placed into the first field of _myid, the second column of the select result gets placed into the second field of _myid.  This is how assignment to row-typed variables (and record-typed too) works in pl/pgsql.

David J.

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Assignment to composite type variable fails inside function but running query separately yields correct type & value ?
Next
From: Tom Lane
Date:
Subject: Re: BUG #16837: Invalid memory access on \h in psql