Hi,
> 2) My second issue is that of a long start up time
I guess there is a connection with an open transaction (an uncommitted
change) that is blocking the transaction log to shrink. Or multiple
connections. This would also explain why it gets slower over time. To find
out, you could use:
j
> How can I truncate the log without starting the database over from> scratch?
CHECKPOINT http://www.h2database.com/html/grammar.html#checkpoint and
probably http://www.h2database.com/html/grammar.html#set_max_log_size
At least in my case, when time to create an index is about 50sec and
every index
a long startup time is also something that would happen if a connection is
holding a transaction open for a long time.
the trace options might help you find this:
http://www.h2database.com/html/features.html#trace_options
zing wrote:
> I'm also having trouble with long startup times - but the ea
I'm also having trouble with long startup times - but the earlier
comments about starting with MVCC off doesn't make work for me.
According to the H2 documentation, MVCC is off by default, and I've
never turned it on.
How can I truncate the log without starting the database over from
scratch?
--
Also note that the mvcc option in h2 is still in beta, so there might still
be bugs lurking in edge cases.
On Sunday, 27 November 2011, Jason wrote:
> I have found a temporary fix to the long start up time: simply connect
> to the database with MVCC off. This action seems to clear the
> transacti
I have found a temporary fix to the long start up time: simply connect
to the database with MVCC off. This action seems to clear the
transaction log after an hour or two. Any re-opening of the database
after this initial connection will be nice and quick. In theory one
could connect with MVCC on, b
Both of those problems sound like one of more of the connections are not
calling commit() after inserting data into the
database, holding the transaction open.
Jason wrote:
> I currently use H2 for a logging/monitoring application which runs
> 24x7 and I am experiencing two issues:
>
> 1) The si
I currently use H2 for a logging/monitoring application which runs
24x7 and I am experiencing two issues:
1) The size of the database constantly grows, and once the size hits
around 250MB it refuses to accept new connections. If the database is
shut down and re-opened the size of the database shri
