Re: Appropriate use of lazy fetching with fetchSize + fetchStream ?

2018-03-08 Thread Lukas Eder
> > For my culture : is this the PortalSuspended and multiple Execute limit 1 > stuff that indicates if it works ? > Probably :) If you want to be sure, I think that the PostgreSQL mailing lists, or Stack Overflow are more appropriate channels... -- You received this message because you are

Re: Appropriate use of lazy fetching with fetchSize + fetchStream ?

2018-03-08 Thread LMey
Alright thanks. I'm seeing this when doing chunks of 1 : -2018-03-08 09:52:59.811 TRACE 28417 --- [ main] o.postgresql.core.v3.QueryExecutorImpl : FE=> Parse(stmt=null,query="REDACTED",oids={1043,0,0}) -2018-03-08 09:52:59.811 TRACE 28417 --- [ main]

Re: Appropriate use of lazy fetching with fetchSize + fetchStream ?

2018-03-08 Thread Lukas Eder
Hello, The API usage is correct: - fetchSize() overrides the JDBC driver's default, which in the case of PostgreSQL is 0 (reading the source code), meaning that all rows are fetched in one go by default. - You're using jOOQ's fetchStream(), which keeps an open JDBC ResultSet