Re: [PATCHES] plpgsql, return can contains any expression - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [PATCHES] plpgsql, return can contains any expression
Date
Msg-id BAY114-F15F05EBE3B03FFDD5A8A37F92E0@phx.gbl
Whole thread Raw
In response to Re: [PATCHES] plpgsql, return can contains any expression  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] plpgsql, return can contains any expression  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>
>"Pavel Stehule" <pavel.stehule@hotmail.com> writes:
> > This patch allows using any row expression in return statement and does
> > transformation from untyped row to composite types if it's necessary.
>
>This patch doesn't seem to cope with cases where the supplied tuple has
>the wrong number of columns, and it doesn't look like it's being careful
>about dropped columns either.  Also, that's a mighty bizarre-looking
>choice of cache memory context in coerce_to_tuple ... but then again,
>why are you bothering with a cache at all for temporary arrays?

I am sorry, Tom. But I don't understand. I can check number of columns,
ofcourse and I'll do it. What cache for temporary arrays do you mean?

Best regards
Pavel Stehule

_________________________________________________________________
Emotikony a pozadi programu MSN Messenger ozivi vasi konverzaci.
http://messenger.msn.cz/


pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: Re: Release notes
Next
From: Andreas Joseph Krogh
Date:
Subject: Wrong list, sorry (was: lower() not working correctly...?)