Skip site navigation (1) Skip section navigation (2)

Re: Where to start for performance problem?

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: MK Spam <mk_spam(at)comcast(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Where to start for performance problem?
Date: 2003-11-25 01:13:51
Message-ID: 3FC2ACCF.2030303@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-performance
> The archives of this list provides many ideas for improving performance, 
> but the problem we are having is gradually degrading performance ending 
> in postgres shutting down.  So it's not a matter of optimizing a complex 
> query to take 5 seconds instead of 60 seconds.  >From what I can tell we 
> are using the VACUUM command on a schedule but it doesn't seem to 
> prevent the database from becoming "congested" as we refer to it.  :]  

Our busy website has a cronjob that runs VACUUM ANALYZE once an hour 
(vacuumdb -a -q -z).

Have you tried going 'VACUUM FULL ANALYZE' (vacuumdb -a -q -z -f) 
instead of a dump and reload?

Chris



In response to

Responses

pgsql-performance by date

Next:From: Greg StarkDate: 2003-11-25 01:16:27
Subject: Re: Maximum Possible Insert Performance?
Previous:From: NidDate: 2003-11-24 22:08:00
Subject: Re: Where to start for performance problem?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group