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

"Jim C. Nasby" <jim@nasby.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.
        regards, tom lane