Re: plpgsql, return can contains any expression - Mailing list pgsql-patches

From Tom Lane
Subject Re: plpgsql, return can contains any expression
Date
Msg-id 13599.1157407876@sss.pgh.pa.us
Whole thread Raw
In response to plpgsql, return can contains any expression  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: plpgsql, return can contains any expression  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
List pgsql-patches
"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?

            regards, tom lane

pgsql-patches by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Information schema - finalize key_column_usage
Next
From: Tom Lane
Date:
Subject: Re: Information schema - finalize key_column_usage