Jeff wrote:
> there you have it. now you can add more commits to badapp or see wtf 
> it is doing or kill it.
> Then at your next cleanup event it should be able to nuke the logs. 
> (if you had a major backup you may want to start a logswtich by 
> calling logswitch_start() so you can get a truncate in there to clear 
> out the dead.  Or you could vac full it, but that tis a silly idea).
Worth observing...

In version 2.0, we no longer *ever* do DELETE against either of the log 
tables; we instead truncate the unused table when there's no data left 
that's accessible.

That should mean that there's no need ever to vacuum these tables.

I'll see if some of this could go into the admin docs.

-- 
(format nil "~S@~S" "cbbrowne" "ca.afilias.info")
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)