Re: pl/pgsql and arrays[] - Mailing list pgsql-general

From Pavel Stehule
Subject Re: pl/pgsql and arrays[]
Date
Msg-id CAFj8pRC8Y3mUhNVF0pTw9Fc5FghrGRG63+kK4V7sUeJUMUvsyQ@mail.gmail.com
Whole thread Raw
In response to Re: pl/pgsql and arrays[]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
2011/12/5 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.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

pgsql-general by date:

Previous
From: "Francisco Figueiredo Jr."
Date:
Subject: Re: What's the best way in Postgres9 to store a bunch of arbitrary boolean values for a row?
Next
From: "C. Mundi"
Date:
Subject: High-Concurrency GiST in postgreSQL