| From: | Marko Kreen <markokr(at)gmail(dot)com> |
|---|---|
| To: | matshyeq <matshyeq(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Daniel Verite *EXTERN* <daniel(at)manitou-mail(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: libpq - lack of support to set the fetch size |
| Date: | 2014-03-12 09:30:01 |
| Message-ID: | 20140312093001.GA13049@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 11, 2014 at 12:39:12PM +0000, matshyeq wrote:
> - when using PQsetSingleRowMode() function - does it give an option to
> define how many rows to cache on client's side (like JDBC setFetchSize()
> does) or leaves it at pqlib's discretion?
This option would not make sense as you are not "fetching" anything,
full resultset is being streamed from server over TCP connection.
> - is it/would it be possible to add corresponding option to pgAdmin to
> limit initially (and each subsequently) returned rows in Query Tool by
> custom defined max value?
It could close connection in the middle of resultset but that seems like
bad idea. LIMIT N or FETCH N are better for such task.
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | matshyeq | 2014-03-12 10:57:03 | Re: libpq - lack of support to set the fetch size |
| Previous Message | Peter Mogensen | 2014-03-12 08:53:52 | Re: Plan rows - 1 or many |