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

Re: postgresql meltdown on

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Aaron Krowne" <akrowne(at)vt(dot)edu>,<pgsql-performance(at)postgresql(dot)org>
Cc: <akrowne(at)vt(dot)edu>
Subject: Re: postgresql meltdown on
Date: 2003-03-17 02:08:10
Message-ID: 021301c2ec2a$10cfca70$6500a8c0@fhp.internal (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
> - Lastly, I tried reducing the shared memory max and limiting postgresql
>   to more conservative values, although still not to the out-of-box
>   values.  Right now shared memory max on the system is 128mb,
>   postgres's shared buffers are at 64mb, sort_mem is at 16mb, and
>   effective cache size is at 10mb.

I found that 5000 shared buffers was best performance on my system.
However, your problems are probably due to maybe not running vacuum,
analyze, reindex, etc.  Your queries may not be effectively indexed -


In response to

pgsql-performance by date

Next:From: Sean ChittendenDate: 2003-03-17 06:10:11
Subject: Re: postgresql meltdown on
Previous:From: Joe ConwayDate: 2003-03-16 11:29:14
Subject: Re: postgresql meltdown on

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