Re: BUG #4533: Plpgsql complex type failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Rod Taylor" <rod(dot)taylor(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4533: Plpgsql complex type failure
Date: 2008-11-22 18:57:10
Message-ID: 29530.1227380230@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Rod Taylor" <rod(dot)taylor(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gregory Stark 2008-11-22 22:56:15 Re: could not read block 77 of relation 1663/16385/388818775
Previous Message Rod Taylor 2008-11-22 18:52:53 Re: BUG #4533: Plpgsql complex type failure