@mdiehl: "Hi all.
I'm doing a routine vacuum on my database and it seems to be getting "stuck."
I've got a "servers" table with only a few rows and columns in it and this is 
what vacuum has to say:
# VACUUM ANALYZE VERBOSE servers;
INFO:  vacuuming "public.servers"
INFO:  scanned index "servers_id" to remove 19200 row versions
DETAIL:  CPU 0.02s/0.01u sec elapsed 0.03 sec.
INFO:  scanned index "servers_name" to remove 19200 row versions
DETAIL:  CPU 0.03s/0.01u sec elapsed 0.05 sec.
The problem is that it's been stalled for several minutes.  It's beginning to 
sound like a hard drive problem.  Any other ideas?
Take care and have fun,
Mike Diehl.
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @tgl: "Mike Diehl <email_address> writes:
<quote>
Maybe it's waiting for some other session to release a page-level lock.
Have you got anything else running in the database, and if so what is
that doing?
			regards, tom lane
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
    @mdiehl: "<quote>
I restarted Postgres and re-ran the vacuum.  All seems OK now.  Thank you for 
your time.  I guess I should have refrained from jumping to conclusions.
Take care and have fun,
Mike Diehl.
Sent via pgsql-general mailing list (<email_address>)
To make changes to your subscription:
<url>"
{'source': 'USENET', 'other_information': '{"reply_count": 2, "forum_name": "pgsql.general.20140811.mbox"}', 'file': 'data/output/usenet-pgsql.general.parquet'}