vacuumdb runtime
I've been lazy and have never run vacuumdb on my development machine. I
decided today that I should, and ran:
vacuumdb --username=foo foo
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.
Anyway I can tell if it's still running/hung? Any estimates on how long
it should take?
Thanks,
-Randy
One more question! Is there a safe way for me to abort it (so I can get
my machine back, and run this after work?)
Thanks!
-Randy
Show quoted text
-----Original Message-----
From: Randall F. Kern
Sent: Monday, May 21, 2001 1:03 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] vacuumdb runtimeI've been lazy and have never run vacuumdb on my development
machine. I
decided today that I should, and ran:vacuumdb --username=foo foo
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.Anyway I can tell if it's still running/hung? Any estimates
on how long
it should take?Thanks,
-Randy---------------------------(end of
broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to
majordomo@postgresql.org
Import Notes
Resolved by subject fallback
"Randall F. Kern" <randy@spoke.net> writes:
One more question! Is there a safe way for me to abort it (so I can get
my machine back, and run this after work?)
Killing the process running VACUUM should work.
regards, tom lane
"Randall F. Kern" <randy@spoke.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
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
Show quoted text
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Monday, May 21, 2001 1:54 PM
To: Randall F. Kern
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] vacuumdb runtime"Randall F. Kern" <randy@spoke.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
Import Notes
Resolved by subject fallback