| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
| Cc: | Eliot Gable <egable+pgsql-general(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: cannot assign non-composite value to a row variable |
| Date: | 2010-06-04 15:23:35 |
| Message-ID: | 15361.1275665015@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> writes:
> I'm pretty sure you have a naming conflict.
Yeah. Specifically, the given example looks like it would try to assign
a null to the target variable, since it'd be taking the null value of a
different variable instead of a value from the intended source.
I believe the bizarre error message is coming from a plpgsql bug that we
fixed in 8.4.3, which basically was that assigning a null to a composite
variable would fail in some cases. If you weren't shooting yourself in
the foot with naming conflicts, you might not trip over that case ...
but an update to 8.4.recent wouldn't be a bad idea anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | erobles | 2010-06-04 15:51:27 | Connection's limit in SCO OpenServer 5.0.7 and pg 8.3.11 (no more than 94 connections) |
| Previous Message | Tom Lane | 2010-06-04 15:09:25 | Re: How can I run an external program from a stored procedure? |