Re: Continual Postgres headaches...

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Weber, Geoffrey M(dot)" <Geoffrey(dot)Weber(at)mcleodusa(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Continual Postgres headaches...
Date: 2007-12-06 19:42:39
Message-ID: b42b73150712061142i80a5ef0jf3d1a3dcec36c86d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Dec 6, 2007 2:22 PM, Weber, Geoffrey M. <Geoffrey(dot)Weber(at)mcleodusa(dot)com> wrote:
> In my efforts to correct these consistency in execution problems, I have
> gone from vacuuming (with analyze) twice a day to every 30 minutes (how long
> it takes a vacuum analyze to run - another seeming problem because it
> shouldn't take so long?). I've done a VACUUM FULL and that sometimes helps,
> but obviously is not a long-term solution for a true OLTP system. Why I
> said "sometimes helps": earlier this week I did a VACUUM FULL, VACUUM
> ANALYZE on the entire schema. A query that was supposed to use the 25MB
> index above (that matched the parameters of the partial index exactly) was
> still not doing so. I had to DROP and re-CREATE the index (and do another
> ANALYZE) to get the database to (correctly) use the index.

you may want to consider using autovacuum. vacuum full is usually not
recommended. maybe you could post some explain analyze of some queries
that are giving you problems?

merlin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-12-06 20:02:31 Re: Recovering data via raw table and field separators
Previous Message John Wells 2007-12-06 19:35:42 Re: Recovering data via raw table and field separators