Re: perf pb solved only after pg_dump and restore

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Guillaume Cottenceau <gc(at)mnc(dot)ch>
Cc: Markus Schaber <schabi(at)logix-tt(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: perf pb solved only after pg_dump and restore
Date: 2006-08-28 16:25:41
Message-ID: 1156782340.10490.9.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, 2006-08-28 at 08:47, Guillaume Cottenceau wrote:
> Markus Schaber <schabi 'at' logix-tt.com> writes:
>
> > > VACUUM ANALYZE is normally run overnight (each night). Is it not
> > > regular enough? There can be hundreds of thousands of statements
> > > a day.
> >
> > Which PostgreSQL version are you using? Maybe you should consider
> > autovacuum (which is a contrib module at least since 7.4, and included
> > in the server since 8.1). If you think that vacuum during working hours
> > puts too much load on your server, there are options to tweak that, at
> > least in 8.1.
>
> Ok, thanks. Unfortunately production insists on sticking on 7.4.5
> for the moment :/

There are known data loss bugs in that version. You should at least
make them update to 7.4.13. Running 7.4.5 instead of 7.4.13 is a bad
decision. Note that there is no need for migrating your data or any of
that with an update within the same major / minor version. As long as
the first two numbers don't change, it's a very simple and fast upgrade.

NOT doing it is negligent.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Merlin Moncure 2006-08-28 19:47:18 Re: Postgre SQL 7.1 cygwin performance issue.
Previous Message Christopher Browne 2006-08-28 16:20:07 Re: Postgre SQL 7.1 cygwin performance issue.