Re: slow pgsql tables - need to vacuum?

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Douglas McNaught <doug(at)mcnaught(dot)org>
Cc: Dan99 <power919(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: slow pgsql tables - need to vacuum?
Date: 2008-04-06 17:49:15
Message-ID: 47F90D1B.4000306@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Douglas McNaught wrote:

> You need to ANALYZE the tables after you load them, and make sure you
> have indexes on the column you're querying (which it sounds like you
> do, but they're not being used because the statistics for the table
> are inaccurate).

I've seen discussion here that made it sound like a REINDEX might also
be required on tables with really high data churn (ie when VACUUM /
VACUUM FULL are run a lot) - if you're not dropping and re-creating the
indexes for better bulk load performance anyway, of course. Am I just
confused, or can this sometimes be necessary?

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2008-04-06 17:56:32 Re: pl/pgsql RECORD data type, how to access to the values
Previous Message Craig Ringer 2008-04-06 17:38:33 Re: Silent install 8.3 diiffers from 8.2