| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brian Cox <brian(dot)cox(at)ca(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: autovacuum hung? |
| Date: | 2009-05-30 15:58:34 |
| Message-ID: | 9708.1243699114@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Brian Cox <brian(dot)cox(at)ca(dot)com> writes:
> autovacuum has been running on 2 tables for > 5 hours. There tables are
> not huge (see below). For the past ~1 hour, I've shut off all other
> activity on this database. The other table being vacuumed has more rows
> (1897810). Anyone have any ideas about why this is taking so long?
Are those processes actually doing anything, or just waiting? strace
or local equivalent would be the most conclusive check.
> cemdb=# select c.oid,c.relname,l.pid,l.mode,l.granted from pg_class c
> join pg_locks l on c.oid=l.relation order by l.pid;
This query isn't very helpful because it fails to show locks that are
not directly associated with tables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2009-05-31 03:41:53 | Re: Scalability in postgres |
| Previous Message | Scott Carey | 2009-05-30 00:48:45 | Re: Scalability in postgres |