On 09/21/2014 03:06 PM, Thomas Kellerer wrote:
> Wouldn't it make more sense to allow for a non-buffered result when
> using auto-commit
> (something like "bufferResults=false") instead?
>
> Or is that technically not possible due to the Postgres wire-protocol?
If you expect the statement to have committed when the execute returns,
then it's not practical.
You could use a WITH HOLD cursor, but that'd be horribly inefficient; it
basically forces the server to buffer the result instead.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services