Daniel Albuschat wrote:

> There's one read-only transaction that selects all datasets from the table.
> There's a second writeable transaction that updates some of the
> selected records after they've been fetched and processed.
>
> Every now and then, but in what seems a specific interval, the
> execution of the update-statement takes exactly 60 seconds.
> I suggest there's some timeout occuring here, but the application has
> exclusive access to the database, so there are no concurrent
> transactions besides the two this application creates.
>
> Do you have any idea what is happening here?

Garbage collection? To test you can, for example, try disabling GC
completely and see if the problem goes away.


--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com