> On Tuesday, November 10, 2020 at 12:03:30 AM UTC-5 val wrote:
> I'm guessing this is how the h2 client/driver (not the db engine it
self) behaves to handle a ResultSet. It will
> fully serialize the contents of the ResultSet to disk first and then
serve that. Perhaps this is
Well here I go into a monologue, answering my own question.
After searching for many fruitless hours, I finally stumbled on a useful
post, here, https://groups.google.com/g/h2-database/c/rgpD_y3Xp7w
Adding *LAZY_QUERY_EXECUTION=1 * to the connection url is closer to what I
was looking for.
On further inspection I can see that H2 is writing a large temp file,
before my results start flowing. 20+ Gigs of data in about 23 minutues.
Likely the whole contents of my large table rewritten to disk.
I'm guessing this is how the h2 client/driver (not the db engine it self)
behaves to
I'm playing around with a large H2 data set.The db in question is 40gb+,
the table has 300 million records.+ Via JDBC.
When I do a simple "select * from mylargetable" it takes 10-15 minute
before I see the first row, and the data starts flowing.
This was unexpected as H2 has been extremely
