| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pl/pgsql and arrays[] |
| Date: | 2011-12-05 16:47:07 |
| Message-ID: | CAFj8pRC8Y3mUhNVF0pTw9Fc5FghrGRG63+kK4V7sUeJUMUvsyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2011/12/5 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> return next in function that returns composite type needs a composite
>> variable. Other cases are not supported there.
>
> Plain "return" has the same limitation, but this really ought to be
> fixed sometime. Composite types have been getting closer and closer
> to first-class status since plpgsql was written.
I sent this patch a few years ago - it was support for RETURN NEXT ROW(...)
but probably there was some issue
Regards
Pavel
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | C. Mundi | 2011-12-05 18:31:09 | High-Concurrency GiST in postgreSQL |
| Previous Message | Francisco Figueiredo Jr. | 2011-12-05 16:41:41 | Re: What's the best way in Postgres9 to store a bunch of arbitrary boolean values for a row? |