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

Re: why can't plpgsql return a row-expression?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: why can't plpgsql return a row-expression?
Date: 2012-10-08 16:21:48
Message-ID: CAFj8pRDg-5d_8O=2q=s_V3uz5cp5Xu_YbhapwvFD5j1LRx3+4w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2012/10/8 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> ERROR:  RETURN must specify a record or row variable in function returning row
>
>> Off the top of my head, I can't think of any reason for this
>> restriction, nor can I find any code comments or anything in the
>> commit log which explains the reason for it.  Does anyone know why we
>> don't allow this?
>
> Laziness, probably.  Feel free to have at it.

I wrote patch some years ago. It was rejected from performance reasons
- because every row had to be casted to resulted type.

Pavel



>
>                         regards, tom lane
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers


In response to

Responses

pgsql-hackers by date

Next:From: Jehan-Guillaume de RorthaisDate: 2012-10-08 16:22:32
Subject: Logging parameters values on bind error
Previous:From: Jeff JanesDate: 2012-10-08 16:15:22
Subject: Re: Warnings from fwrite() in git head

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