| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Roger Pack <rogerdpack2(at)gmail(dot)com> |
| Cc: | pgsql-jdbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Not overflow RAM with default fetchSize? |
| Date: | 2022-04-27 14:44:28 |
| Message-ID: | CADK3HHKY_Uoc=_r=QMCg-MowuF1sinR=HJ_NMCVEdgqyoGnTsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Please post an issue on github for this.
Issues · pgjdbc/pgjdbc (github.com)
<https://github.com/pgjdbc/pgjdbc/issues>
Dave Cramer
www.postgres.rocks
On Fri, 22 Apr 2022 at 13:45, Roger Pack <rogerdpack2(at)gmail(dot)com> wrote:
> Might be nice to have the default fetch size be a "reasonably
> performant" number, with the default (unlimited), it can overflow
> memory for large queries which is confusing. Or at least it used to,
> I haven't tested it in awhile.
> Cheers!
> -=roger=
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2022-04-27 14:47:04 | Re: BUG #17467: Perf degradation after switching to latest jdbc drivers |
| Previous Message | Dave Cramer | 2022-04-27 14:43:21 | Re: Why does the prepareThreshold=0 (to cover pgbouncer transaction mode) disables protocol binary transfers ? (w/ PoC patch and measurements) |