| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jaime Soler <jaime(dot)soler(at)gmail(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, Brad DeJong <bpd0018(at)gmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: ResultSet storing all rows with defaulftFetchSize to 5000 |
| Date: | 2018-02-12 16:21:00 |
| Message-ID: | CAB=Je-G-_m46JH85Sg=PAg3BqExF-oELutUxNipaJMW-v_CemA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>(Yes, we do support WITH HOLD.)
Oh, is it something available through extended query protocol?
The documentation says "If successfully created, a named portal object
lasts till the end of the current transaction, unless explicitly destroyed",
however I just hope it is a documentation bug and one can create a named
portal that can survive transaction end.
I don't think explicit "fetch ... from ..." is a workable solution for
pgjdbc as it would incur high overhead (both maintenance, and performance):
1) declare ... binary is either full-binary or full text. pgjdbc implements
just a subset of binary formats
2) `fetch ...` cannot be prepared, so I expect more network traffic and
parse/execute overhead
3) Reimplementing "frontend" from "ExtendedQuery" to "Declare/fetch" is a
great amount of work
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-12 16:39:08 | Re: ResultSet storing all rows with defaulftFetchSize to 5000 |
| Previous Message | Dave Cramer | 2018-02-12 16:12:57 | Re: ResultSet storing all rows with defaulftFetchSize to 5000 |