pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: rapid degradation after postmaster restart
Date: Wed, 17 Mar 2004 15:57:09 -0500
Message-ID: <4058BBA5.4080002@zeut.net> (raw)
In-Reply-To: <20040317181115.GA7805@phlogiston.dyndns.org>
References: <4052661D.5060505@joeconway.com>
	<20040317181115.GA7805@phlogiston.dyndns.org>

Andrew Sullivan wrote:

>The vacuum delay stuff that you're working on may help, but I can't
>really believe it's your salvation if this is happening after only a
>few minutes.  No matter how much you're doing inside those functions,
>you surely can't be causing so many dead tuples that a vacuum is
>necessary that soon.  Did you try not vacuuming for a little while to
>see if it helps?
>  
>

Some of this thread was taken off line so I'm not sure it was mentioned 
on the list, but a big part of the problem was that Joe was running into 
the same bug that Cott Lang ran into a while ago which caused the vacuum 
threshold to get set far too low resulting in vacuums far too often..  
This has been fixed and the patch has been committed unfortunately it 
didn't make it into 7.4.2, but it will be in 7.4.3 / 7.5.

>I didn't see it anywhere in this thread, but are you quite sure that
>you're not swapping?  Note that vmstat on multiprocessor Solaris
>machines is not notoriously useful.  You may want to have a look at
>what the example stuff in the SE Toolkit tells you, or what you get
>from sar.  I believe you have to use a special kernel setting on
>Solaris to mark shared memory as being ineligible for swap.
>  
>

I haven't heard from Joe how things are going with the fixed 
pg_autovacuum but that in combination with the vacuum delay stuff should 
work well.

Matthew






view thread (26+ messages)

Message-ID: <4058BBA5.4080002@zeut.net>
Permalink:  ../4058BBA5.4080002@zeut.net/
Also on:    postgresql.org/message-id/4058BBA5.4080002@zeut.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: matthew@zeut.net, ajs@crankycanuck.ca
  Subject: Re: rapid degradation after postmaster restart
  In-Reply-To: <4058BBA5.4080002@zeut.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox