Re: Strange performance degradation

From: Lorenzo Allegrucci <lorenzo(dot)allegrucci(at)forinicom(dot)it>
To: pgsql-performance(at)postgresql(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Strange performance degradation
Date: 2009-11-20 20:26:10
Message-ID: 4B06FB62.7080907@forinicom.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance

Brian Modra wrote:
> I had a similar problem: I did a large delete, and then a selct which
> "covered" the previous rows.
> It took ages, because the index still had those deleted rows.
> Possibly the same happens with update.
>
> Try this:
> vacuum analyse
> reindex database ....
> (your database name instead of ...)
>
> or, rather do this table by table:
> vacuum analyse ....
> reindex table ...
>
>
> Autovacuum is a generally good thing.
>
>> So, my main question is.. how can just a plain simple restart of postgres
>> restore the original performance (3% cpu time)?
>
> there were probably some long transactions running. Stopping postgres
> effectively kills them off.

I'll try that, thanks for your help Brian.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message akp geek 2009-11-20 20:38:14 PG_STANDBY ISSUE
Previous Message Lorenzo Allegrucci 2009-11-20 20:24:38 Re: Strange performance degradation

Browse pgsql-performance by date

  From Date Subject
Next Message Thom Brown 2009-11-20 20:35:58 Re: Postgres query completion status?
Previous Message Lorenzo Allegrucci 2009-11-20 20:24:38 Re: Strange performance degradation