Opened 9 years ago
Last modified 8 years ago
#2009 closed defect
PostgreSQL seems to be loading entire result set into memory — at Version 1
| Reported by: | Nicklas Nordborg | Owned by: | everyone |
|---|---|---|---|
| Priority: | critical | Milestone: | BASE 3.9 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description (last modified by )
This was investigated for MySQL a long time ago and resulted in setting some parameters on the connection string (useCursorFetch=true&defaultFetchSize=100&useServerPrepStmts=true, see #953).
I guess the corresponding investigations were never made for PostgreSQL because it seems like the JDBC driver is loading the entire resultset into memory (this was seen when testing the Reggie release exporter http://baseplugins.thep.lu.se/ticket/887).
We need to investigate and make sure that PostgreSQL is using server-side cursors for streaming the result.
Change History (2)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|
by , 9 years ago
| Attachment: | loading-142-out-of-memory.png added |
|---|
Note:
See TracTickets
for help on using tickets.
Trying to load 142 x 100k raw data entries