Re: My quick and dirty "solution" (Re: Performance Problem with Vacuum of bytea table (PG 8.0.13))

From: Bastian Voigt <post(at)bastian-voigt(dot)de>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: My quick and dirty "solution" (Re: Performance Problem with Vacuum of bytea table (PG 8.0.13))
Date: 2007-05-25 14:06:14
Message-ID: 4656ED56.608@bastian-voigt.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Kristo Kaiv wrote:
> you should first cluster the table on primary key.
> The table is probably already bloated from the 3 hr delay it had before.
> First
> CLUSTER "primary key index name" ON group_fin_account_tst;
> Then
> vacuum it every 3 minutes.
> NB! clustering takes an access exclusive lock on table
Kristo,
thanks a bunch!!
This was the solution...
The cluster operation took about 60sec, and after it was done the vacuum
finished in only 10sec. or so, with no noticeable performance
bottleneck. Now vacuum is running every 2-3 minutes and makes no problems.

Hhhh, now I can look forward to a laid-back weekend..

Richard, Kristo, Alvaro, thanks 1000 times for responding so quickly

:-)

--
Bastian Voigt
Neumünstersche Straße 4
20251 Hamburg
telefon +49 - 40 - 67957171
mobil +49 - 179 - 4826359

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2007-05-25 14:07:14 Re: general PG network slowness (possible cure) (repost)
Previous Message Peter T. Breuer 2007-05-25 14:02:21 Re: general PG network slowness (possible cure) (repost)