Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: dbt-2 tuning results with postgresql-8.3.5
- 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: Tue, 23 Dec 2008 09:01:06 -0300
- Message-id: <20081223120106.GC6217@alvh.no-ip.org> <text/plain>
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
- References:
- dbt-2 tuning results with postgresql-8.3.5
- From: Mark Wong
- Re: dbt-2 tuning results with postgresql-8.3.5
- From: Gregory Stark
- Re: dbt-2 tuning results with postgresql-8.3.5
- From: Mark Wong
- Re: dbt-2 tuning results with postgresql-8.3.5
- From: Gregory Stark
- Re: dbt-2 tuning results with postgresql-8.3.5
- From: Mark Wong
- Re: dbt-2 tuning results with postgresql-8.3.5
- From: Gregory Stark
- Re: dbt-2 tuning results with postgresql-8.3.5
- From: Mark Wong
- dbt-2 tuning results with postgresql-8.3.5
- Prev by Date: Re: dbt-2 tuning results with postgresql-8.3.5
- Next by Date: How to "unique-ify" HUGE table?
- Previous by thread: Re: dbt-2 tuning results with postgresql-8.3.5
- Next by thread: Re: dbt-2 tuning results with postgresql-8.3.5
- Indexes: