Re: BUG #4533: Plpgsql complex type failure - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4533: Plpgsql complex type failure
Date
Msg-id 29530.1227380230@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4533: Plpgsql complex type failure  ("Rod Taylor" <rod.taylor@gmail.com>)
List pgsql-bugs
"Rod Taylor" <rod.taylor@gmail.com> writes:
> That was the short form exhibiting the bug. Selecting the complex
> column from a table into a value results in the same error.

Well, you could do "SELECT t.* INTO v_time".  The fundamental point here
is that when the INTO target is a rowtype variable, plpgsql expects to
assign the columns of the SELECT result to the fields of the variable.
We can't change that without breaking enormous amounts of existing code.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4533: Plpgsql complex type failure
Next
From: Gregory Stark
Date:
Subject: Re: could not read block 77 of relation 1663/16385/388818775