| From: | "Oleg Serov" <serovov(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Bug with FOR ... LOOP and composite types |
| Date: | 2008-09-03 14:33:13 |
| Message-ID: | cec7c6df0809030733i16ce630euda20292f10f50a4d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Yes, you are right, with record type working correct;
Thanks
2008/9/2 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> "Oleg Serov" <serovov(at)gmail(dot)com> writes:
> > But if there are some records in t_table and we romove WHERE 1=0, we will
> > have
> > ERROR: wrong record type supplied in RETURN NEXT CONTEXT: PL/pgSQL
> function
> > "t_func" line 9 at RETURN NEXT
>
> I couldn't reproduce that here, at least not with versions newer than
> 8.0. Maybe you were testing a case that also involved dropped columns?
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira de Oliveira | 2008-09-03 15:38:40 | Re: BUG #4397: crash in tab-complete.c |
| Previous Message | Rudolf Leitgeb | 2008-09-03 14:31:30 | BUG #4397: crash in tab-complete.c |