| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kim <kim(at)myemma(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: unusual performance for vac following 8.2 upgrade |
| Date: | 2007-01-11 18:17:44 |
| Message-ID: | 27678.1168539464@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Kim <kim(at)myemma(dot)com> writes:
> Running a vac on an 8.2 client connecting to an 8.2 database (following
> example was for a 14 row static table) - vacuums will sit (for lack of a
> better word) for anywhere from ten to twenty minutes before taking a
> lock out on the table and doing work there.
How big is this database (how many pg_class entries)? What do you get
from "VACUUM VERBOSE pg_class"? The truss results make it sound like
the problem is pgstat_vacuum_tabstat() taking a long time, but that code
has not changed since 8.1 ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-11 18:20:52 | Re: unusual performance for vac following 8.2 upgrade |
| Previous Message | Bruce Momjian | 2007-01-11 18:17:42 | Re: pgindent infelicity |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-11 18:20:52 | Re: unusual performance for vac following 8.2 upgrade |
| Previous Message | Carlos H. Reimer | 2007-01-11 18:17:06 | Improving SQL performance |