RE: vacuumdb runtime

That was it! I had a weeks old hung test app running in the background.
Once I stopped that (closing the postgres transaction), vacuum took
about 30 seconds.

Thanks,
-Randy

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Monday, May 21, 2001 1:54 PM
> To: Randall F. Kern
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] vacuumdb runtime
>
>
> "Randall F. Kern" <randy(at)spoke(dot)net> writes:
> > After giving me several 'NOTICE: Skipping "pg_foo" -- only
> table owner
> > can VACUUM it' messages, it's been running along for the
> last 2 hours.
> > No postgres processes appear very high in "top", and the
> data directory
> > is about 100MB.
>
> Seems unlikely that vacuum is actually doing anything, if you
> can't see
> it in 'top'. Perhaps it is sitting waiting to acquire a lock on some
> table --- do you have any other open transactions?
>
> regards, tom lane
>