Yeah, I don't really understand that part either. Sorry, but I'm also out of enthusiasm for chasing this bug.
On 2013-08-22 13:27, Davide Cavestro wrote:
I still don't understand why the transaction log is taking up more space than expected, even when using /setString()/ and autocommit: that's what happens with the test case I attached to my previous message.On Thursday, August 22, 2013 1:14:27 PM UTC+2, Noel Grandin wrote: On 2013-08-22 12:42, Davide Cavestro wrote:Before giving up definitively, could you please tell me if getting the /pageStore: Transaction log could not be truncated; size: 16 MB / warning in the trace file indicates an error?No, it's just a warning. It's a useful one, because it indicates that the transaction log is taking up more space than we expect, and that there might be a problem somewhere else. I think we've got to the bottom to this - it is related to the use of setCharacterStream(), which generates temporary LOB's which clog up the transaction log. Myself and Thomas are working through some patches, we should have something in a couple of days.
-- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
