Re: degenerate performance on one server of 3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Erik Aronesty <erik(at)q32(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: degenerate performance on one server of 3
Date: 2009-06-01 03:40:15
Message-ID: 27485.1243827615@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> Tom Lane wrote:
>> I'm betting on varying degrees of table bloat. Have you tried vacuum
>> full, cluster, etc?

> Or, if you have been using VACUUM FULL, try REINDEXing the tables,
> because it could easily be index bloat. Clustering the table will take
> care of index bloat as well as table bloat.

Index bloat wouldn't explain the slow-seqscan behavior the OP was
complaining of. Still, you're right that if the tables are bloated
then their indexes probably are too ... and that VACUUM FULL alone
will not fix that.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Erik Aronesty 2009-06-01 04:12:57 Re: degenerate performance on one server of 3
Previous Message Craig Ringer 2009-06-01 03:28:51 Re: degenerate performance on one server of 3