| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Dave Cramer' <pg(at)fastcrypt(dot)com>, Jorge Solórzano <jorsol(at)gmail(dot)com> |
| Cc: | Vitalii Tymchyshyn <vit(at)tym(dot)im>, Mark Rotteveel <mark(at)lawinegevaar(dot)nl>, List <pgsql-jdbc(at)postgresql(dot)org>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Subject: | Re: [RFC] How about changing the default value of defaultRowFetchSize? |
| Date: | 2016-10-24 03:12:07 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F63569F@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
From: pgsql-jdbc-owner(at)postgresql(dot)org
> [mailto:pgsql-jdbc-owner(at)postgresql(dot)org] On Behalf Of Dave Cramer
> defaultRowFetchSize is not an internal number. If you set the
> property you get the value of the property.
>
>
>
>
> That I agree with. If you don't set it you get 0
You will get the value of defaultRowFetchSize if you don't call setFetchSize(), and the default value of defaultRowFetchSize will be, say, 100. As I mentioned in the previous mail, I think getFetchSize() returns the actual number of rows, not the hint (0).
Any comments on the default value of defaultRowFetchSize? There was a request for 1,000. I think 100 would be sufficient, considering the typical web pagination, for example. Those who want to speed up batch apps by reducing round trips can find the parameter and/or setFetchSize() and use them.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2016-10-24 10:36:31 | Re: Patch: Implement failover on libpq connect level. |
| Previous Message | Dave Cramer | 2016-10-23 22:06:50 | Re: [RFC] How about changing the default value of defaultRowFetchSize? |