Re: why can't plpgsql return a row-expression? - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: why can't plpgsql return a row-expression?
Date
Msg-id CAFj8pRDg-5d_8O=2q=s_V3uz5cp5Xu_YbhapwvFD5j1LRx3+4w@mail.gmail.com
Whole thread Raw
In response to Re: why can't plpgsql return a row-expression?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: why can't plpgsql return a row-expression?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2012/10/8 Tom Lane <tgl@sss.pgh.pa.us>:
> Robert Haas <robertmhaas@gmail.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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers



pgsql-hackers by date:

Previous
From: Jehan-Guillaume de Rorthais
Date:
Subject: Logging parameters values on bind error
Next
From: Peter Geoghegan
Date:
Subject: Re: sortsupport for text