On Feb 8, 2012, at 17:05 , Richard Hipp wrote:
I generally don't stress over a 10MB file on my 1TB disk drive, though...
Still, it probably would not hurt to have Fossil do vacuum from time to time,
would it?
Kind regards,
Remigiusz Modrzejewski
On Tue, Feb 7, 2012 at 19:26, Richard Hipp d...@sqlite.org wrote:
The _FOSSIL_ file contains (among other things) your stash and your undo
history. What does
sqlite3_analyzer _FOSSIL_
Hmm, I just compliled/installed sqlite-3.7.10 from its fossil repo and
it did build sqlite3 executable
On Wed, Feb 8, 2012 at 9:10 AM, Leo Razoumov slonik...@gmail.com wrote:
On Tue, Feb 7, 2012 at 19:26, Richard Hipp d...@sqlite.org wrote:
The _FOSSIL_ file contains (among other things) your stash and your undo
history. What does
sqlite3_analyzer _FOSSIL_
Hmm, I just
On Tue, Feb 7, 2012 at 19:26, Richard Hipp d...@sqlite.org wrote:
On Tue, Feb 7, 2012 at 7:24 PM, Leo Razoumov slonik...@gmail.com wrote:
Hi List,
I wonder why _FOSSIL_ file grows so fast. I did some little work with
a clone of fossil source code repository (23MB) and over space of two
days
On Wed, Feb 08, 2012 at 10:16:24AM -0500, Leo Razoumov wrote:
The _FOSSIL_ file contains (among other things) your stash and your undo
history. What does
sqlite3_analyzer _FOSSIL_
show you? Which tables are using the most space. Maybe it just needs to be
vacuumed?
Looks to me
2012/2/8 Lluís Batlle i Rossell vi...@viric.name
On Wed, Feb 08, 2012 at 10:16:24AM -0500, Leo Razoumov wrote:
The _FOSSIL_ file contains (among other things) your stash and your
undo
history. What does
sqlite3_analyzer _FOSSIL_
show you? Which tables are using the most
On Wed, Feb 8, 2012 at 11:05, Richard Hipp d...@sqlite.org wrote:
Probably what happened is that you did some operation that created a large
undo stack, which was stored in the _FOSSIL_ file. Then later, after the
undo expired, that space was freed. If the space utilization is an issue
for
On Wed, Feb 8, 2012 at 11:05, Richard Hipp d...@sqlite.org wrote:
Probably what happened is that you did some operation that created a large
undo stack, which was stored in the _FOSSIL_ file. Then later, after the
undo expired, that space was freed. If the space utilization is an issue
for
On Wed, Feb 8, 2012 at 11:53 AM, Leo Razoumov slonik...@gmail.com wrote:
On Wed, Feb 8, 2012 at 11:05, Richard Hipp d...@sqlite.org wrote:
Probably what happened is that you did some operation that created a
large
undo stack, which was stored in the _FOSSIL_ file. Then later, after
the
Hi List,
I wonder why _FOSSIL_ file grows so fast. I did some little work with
a clone of fossil source code repository (23MB) and over space of two
days _FOSSIL_ reached 10MB. What gives?
--Leo--
___
fossil-users mailing list
On Tue, Feb 7, 2012 at 7:24 PM, Leo Razoumov slonik...@gmail.com wrote:
Hi List,
I wonder why _FOSSIL_ file grows so fast. I did some little work with
a clone of fossil source code repository (23MB) and over space of two
days _FOSSIL_ reached 10MB. What gives?
The _FOSSIL_ file contains
11 matches
Mail list logo
