[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Uncommitted transactions

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 17 Aug 2009 11:40:32 -0400

Vyacheslav V. Zholudev wrote:
> Hi guys,
> sorry if this question has been discussed somewhere, but I didn't find
> an answer yet.
> I will talk about BDB-based repositories.
> What happens with values in 'strings' table that have been written but
> the SVN transaction was not committed (nor aborted) due to e.g. network
> failure.
> Will this values will be cleaned up from BDB on the next commit, or when
> invoking 'cleanup' command, or when executing svnadmin with parameters
> to delete 'dead' transactions, or smth else?

If a failed commit is cleanly aborted (which Subversion attempts to do when
possible), then all the data associated with the transaction should be
purged from the back-ends. Sometimes commits aren't cleanly aborted,
though, and Subversion doesn't try to guess which commit transactions are
stale versus maybe just long-lived because the client connections are
unnaturally slow. This is why we provide administrators with the 'svnadmin
lstxns' and 'svnadmin rmtxns' subcommands.

(By the way, this question belongs on the users@ list, as it has nothing to
do with discussing the development of Subversion itself.)

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2009-08-17 17:40:50 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.