Skip site navigation (1) Skip section navigation (2)

Re: plpgsql, return can contains any expression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org, neilc(at)samurai(dot)com
Subject: Re: plpgsql, return can contains any expression
Date: 2006-09-04 22:11:16
Message-ID: 13599.1157407876@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2006-09-04 22:11:53
Subject: Re: [PATCHES] Trivial patch to double vacuum speed on tables with no indexes
Previous:From: Greg Sabino MullaneDate: 2006-09-04 22:04:24
Subject: Re: Information schema - finalize key_column_usage

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2006-09-04 22:11:53
Subject: Re: [PATCHES] Trivial patch to double vacuum speed on tables with no indexes
Previous:From: Greg Sabino MullaneDate: 2006-09-04 22:04:24
Subject: Re: Information schema - finalize key_column_usage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group