| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Mark Wong <markwkm(at)gmail(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Selena Deckelmann <selenamarie(at)gmail(dot)com>, Gabrielle Roth <gorthx(at)gmail(dot)com> |
| Subject: | Re: dbt-2 tuning results with postgresql-8.3.5 |
| Date: | 2008-12-23 12:01:06 |
| Message-ID: | 20081223120106.GC6217@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Mark Wong escribió:
> Hrm, tracking just the launcher process certainly doesn't help. Are
> the spawned processed short lived? I take a snapshot of
> /proc/<pid>/io data every 60 seconds.
The worker processes can be short-lived, but if they are, obviously they
are not vacuuming the large tables. If you want to track all autovacuum
actions, change autovacuum_log_min_messages to 0.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kynn Jones | 2008-12-23 17:25:48 | How to "unique-ify" HUGE table? |
| Previous Message | Greg Smith | 2008-12-23 03:51:08 | Re: dbt-2 tuning results with postgresql-8.3.5 |