Re: SQL functions, INSERT/UPDATE/DELETE RETURNING, and

Hi, Tom,

Tom Lane wrote:
> "Jim C. Nasby" <jim(at)nasby(dot)net> writes:
>> The specific concern I have is large result sets, like 10s or 100s of MB
>> (or more). We just added support for not buffering those in psql, so it
>> seems like a step backwards to have the backend now buffering it (unless
>> I'm confused on how a tuplestore works...)
>
> Well, a tuplestore can dump to disk, so at least you don't need to worry
> about out-of-memory considerations.

Would it be possible to kinda "wrap" the query execution into the
tuplestore interface, so that the tuples are generated "on the fly" when
fetched from the tuplestore, for large resultsets?

Thanks,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org