X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id 459B39FD055
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 28 Aug 2006 13:25:52 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 26496-01 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Mon, 28 Aug 2006 16:25:42 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from exchange.g2switchworks.com (mail.g2switchworks.com
	[63.87.162.25]) by postgresql.org (Postfix) with ESMTP id ED7049FD054
	for <pgsql-performance@postgresql.org>;
	Mon, 28 Aug 2006 13:25:41 -0300 (ADT)
Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com
	([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ;
	Mon, 28 Aug 2006 16:25:41 +0000
Received: from state.g2switchworks.com by mail.g2switchworks.com;
	28 Aug 2006 11:25:41 -0500
Subject: Re: perf pb solved only after pg_dump and restore
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Guillaume Cottenceau <gc@mnc.ch>
Cc: Markus Schaber <schabi@logix-tt.com>, pgsql-performance@postgresql.org
In-Reply-To: <87ac5px98h.fsf@meuh.mnc.lan>
References: <8764gd1dkz.fsf@meuh.mnc.lan> <44F2B737.7070301@logix-tt.com>
	<87sljhyz4b.fsf@meuh.mnc.lan>
	<1d4e0c10608280317i4eb9d7d0r2b397845ffb8c19d@mail.gmail.com>
	<874pvxyrbg.fsf@meuh.mnc.lan> <44F2EC0C.7090407@logix-tt.com>
	<87ac5px98h.fsf@meuh.mnc.lan>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1156782340.10490.9.camel@state.g2switchworks.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) 
Date: Mon, 28 Aug 2006 11:25:41 -0500
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=SPF_PASS,
	UNPARSEABLE_RELAY
X-Spam-Level: 
X-Archive-Number: 200608/447
X-Sequence-Number: 20632

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.