| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Disk buffering of resultsets |
| Date: | 2014-09-21 07:24:06 |
| Message-ID: | 541E7D16.8040405@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-09-21 07:35:31 | Re: Disk buffering of resultsets |
| Previous Message | Craig Ringer | 2014-09-21 07:18:41 | Re: Disk buffering of resultsets |