Re: Possible explanations for catastrophic performace deterioration?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
Cc: "Carlos Moreno" <moreno_pg(at)mochima(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Possible explanations for catastrophic performace deterioration?
Date: 2007-09-23 17:27:35
Message-ID: 21428.1190568455@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> My guess is that a vacuum full would've brought the other database
> back up to speed.

Yeah, table bloat is what it sounds like to me too.

> In the future, you probably want to set fillfactor
> to a reasonable amount to account for updates-to-blocks-between-vacuum
> to try and capture as few row-migrations as possible.

More to the point, check your FSM size and make sure vacuums are
happening often enough.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Carlos Moreno 2007-09-23 18:15:09 Re: Possible explanations for catastrophic performace deterioration?
Previous Message Yinan Li 2007-09-23 17:00:24 zero value in statistics collector's result