MK Spam <[EMAIL PROTECTED]> wrote:
> ... the problem we are having is gradually degrading
> performance ending in postgres shutting down.
As someone else commented, that's not an ordinary sort of performance
problem. What exactly happens when the database "shuts down"?
re
On Mon, Nov 24, 2003 at 16:03:17 -0600,
MK Spam <[EMAIL PROTECTED]> wrote:
>
> 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 c
The problems with giving suggestions about increasing performance is
that one persons increase is another persons decrease.
having said that, there are a few general suggestions :
Set-up some shared memory, about a tenth of your available RAM, and
configure shared_memory and max_clients correct
Nid wrote:
I've been digging around in the code and found where we are executing the
VACUUM command. VACUUM ANALYZE is executed every 15 minutes. We haven't
tried VACUUM FULL ANALYZE. I think I read that using FULL is a good idea
once a day or something. Just doing a VACUUM ANALYZE doesn't see
27;t seem to be
preventing our problem. Thank you for the responses.
nid
- Original Message -
From: "Christopher Kings-Lynne" <[EMAIL PROTECTED]>
To: "MK Spam" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 24, 2003 7:13 PM
Subject:
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
] Where to start for
performance problem?
I've scanned some of the archives and have
learned a lot about different performance tuning practices. I will be
looking into using many of these ideas but I'm not sure they address the issue
I am currently experiencing.
Fir
I've scanned some of the archives and have learned
a lot about different performance tuning practices. I will be looking into
using many of these ideas but I'm not sure they address the issue I am currently
experiencing.
First, I'm a total newb with postgresql. Like
many before me, I hav
