From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Disk buffering of resultsets |
Date: | 2014-09-22 21:55:59 |
Message-ID: | CADK3HHK3CmJvJgoxALu3XVDZ449x8mzeF=5Xx-ANV5g62wriAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On 22 September 2014 17:17, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 9/22/2014 2:04 PM, Lussier, Denis wrote:
>
>> I like Craig's idea to use the jdk7 temp file handling. I propose to
>> this project keep it simple (at least at first) and start with this as a
>> jdbc41 only feature.
>>
>> Many people use pgjdbc for OLTP style transactions and wouldn't ever want
>> to spill to disk. This is why (IMHO) the algorithm that determines under
>> which stress
>> condition this feature uses (assuming it is enabled) is so critical.
>>
>>
> this still won't address the issue that the postgresql server itself ALSO
> marshals the entire result set into ITS memory before sending it to the
> client. Really, using cursors for large result-sets is the correct way to
> go.
>
>
>
Clearly, but not everyone has this option. I don't really see this as a
valid reason not to implement this.
Dave
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-09-23 00:46:15 | Re: Disk buffering of resultsets |
Previous Message | John R Pierce | 2014-09-22 21:17:36 | Re: Disk buffering of resultsets |