On Tue, Mar 27, 2012 at 09:53:38AM -0700, Pete scratched on the wall:
> Interesting. Does that mean any open transaction other than the VACUUM
> transaction? I'm still confused.
The database connection running the VACUUM command cannot currently
be in a transaction, nor can there be any active (stepping) statements
associated with the connection (which would have an implied transaction).
Other connections can be doing whatever they want, but the VACUUM
command needs a full set of locks to run. Normal locking policy
applies.
-j
> On Tue, Mar 27, 2012 at 9:00 AM, <[email protected]> wrote:
> > Date: Mon, 26 Mar 2012 10:25:49 -0700 (PDT)
> > From: Peter Aronson <[email protected]>
> > To: General Discussion of SQLite Database <[email protected]>
> > Subject: Re: [sqlite] VACUUMing large DBs
> > Message-ID:
> > <[email protected]>
> > Content-Type: text/plain; charset=iso-8859-1
> >
> > Actually, it can't be in a transaction.? To quote: "A VACUUM will fail if
> > there
> > is an open transaction, or if there are one or more active SQL statements
> > when
> > it is run."? (See http://www.sqlite.org/lang_vacuum.html).
--
Jay A. Kreibich < J A Y @ K R E I B I.C H >
"Intelligence is like underwear: it is important that you have it,
but showing it to the wrong people has the tendency to make them
feel uncomfortable." -- Angela Johnson
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
