| From: | Vitalii Tymchyshyn <vit(at)tym(dot)im> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, John R Pierce <pierce(at)hogranch(dot)com>, PG-JDBC Mailing List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Disk buffering of resultsets |
| Date: | 2014-10-05 03:24:45 |
| Message-ID: | CABWW-d0bNau=Ypx2iidbmMeuA8ks75xn=dNv7n4m_XEHz8wJkg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hello, all
I've made a draft implementation of setFetchSize in autocommit mode here:
https://github.com/tivv/pgjdbc/tree/autocommit_fetchsize
Tests look good.
Note that it does not try to limit Execute size as I don't think I
understand protocol fully. The only thing it does is that it does not read
everything before returning to the caller. Instead it reads response rows
in fetchSize batches. If another statement tries to use the same
connection, full result is read immediatelly (this part is not tested yet).
Best regards, Vitalii Tymchyshyn
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-10-06 01:53:31 | Re: Disk buffering of resultsets |
| Previous Message | Vitalii Tymchyshyn | 2014-10-04 19:16:35 | Re: Disk buffering of resultsets |