Re: Continual Postgres headaches...

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Weber, Geoffrey M(dot)" <Geoffrey(dot)Weber(at)mcleodusa(dot)com>
Subject: Re: Continual Postgres headaches...
Date: 2007-12-07 17:26:10
Message-ID: 200712071226.11311.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday 06 December 2007 20:00, Tom Lane wrote:
> "Weber, Geoffrey M." <Geoffrey(dot)Weber(at)mcleodusa(dot)com> writes:
> > My problems really are with performance consistency. I have tweaked the
> > execution so that everything should run with sub-second execution times,
> > but even after everything is running well, I can get at most a week or
> > two of steady running before things start to degrade.
>
> Aside from the other responses: gradual degradation over a period of
> time sounds like a bloat problem to me. You should monitor table and
> index sizes to confirm or deny that and find out just what's bloating.
> Switching to autovacuum, or a better-designed manual vacuum schedule,
> might be the ultimate answer, but first you need some concrete data
> about what's going wrong. Otherwise you're just shooting in the dark.
>

just to add, make sure your free_space_map settings are set adequately;
otherwise you might not be able to find an adequate schedule.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Howard Cole 2007-12-07 17:30:00 Killing a session in windows
Previous Message John D. Burger 2007-12-07 17:26:06 How to EXPLAIN statements inside a trigger function?