Re: Stuck vacuum... - Mailing list pgsql-general

From Tom Lane
Subject Re: Stuck vacuum...
Date
Msg-id 26945.1255141372@sss.pgh.pa.us
Whole thread Raw
In response to Stuck vacuum...  (Mike Diehl <mdiehl@diehlnet.com>)
Responses Re: Stuck vacuum...
List pgsql-general
Mike Diehl <mdiehl@diehlnet.com> writes:
> 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?

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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans
Next
From: Tom Lane
Date:
Subject: Re: Regexp confusion