From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mike Diehl <mdiehl(at)diehlnet(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Stuck vacuum... |
Date: | 2009-10-10 02:22:52 |
Message-ID: | 26945.1255141372@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mike Diehl <mdiehl(at)diehlnet(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Nick | 2009-10-10 02:23:46 | Access dynamic NEW.column_name in trigger? |
Previous Message | Tom Lane | 2009-10-10 02:11:39 | Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans |