pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Markus Schaber <schabi@logix-tt.com>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: Bealach-na Bo <bealach_na_bo@hotmail.com>
Cc: ahodgson@simkin.ca
Cc: pgsql-performance@postgresql.org
Subject: Re: Why so slow?
Date: Tue, 02 May 2006 19:16:12 +0200
Message-ID: <445793DC.40401@logix-tt.com> (raw)
In-Reply-To: <20060430100346.20f010a9.wmoran@collaborativefusion.com>
References: <200604281043.16083@hal.medialogik.com>
	<BAY101-F38A0FADC87E67C062FE5E1ADB00@phx.gbl>
	<20060430100346.20f010a9.wmoran@collaborativefusion.com>

Hi, Bill,

Bill Moran wrote:

> My understanding is basically that if you vacuum with the correct
> frequency, you'll never need to vacuum full.  This is why the
> autovacuum system is so nice, it adjusts the frequency of vacuum according
> to how much use the DB is getting.

Additonally, the "free_space_map" setting has to be high enough, it has
to cover enough space to put in all pages that get dead rows between two
vacuum runs.

HTH,
Markus


-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org



view thread (26+ messages)  latest in thread

Message-ID: <445793DC.40401@logix-tt.com>
Permalink:  ../445793DC.40401@logix-tt.com/
Also on:    postgresql.org/message-id/445793DC.40401@logix-tt.com

 · 

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: schabi@logix-tt.com, wmoran@collaborativefusion.com, bealach_na_bo@hotmail.com, ahodgson@simkin.ca
  Subject: Re: Why so slow?
  In-Reply-To: <445793DC.40401@logix-tt.com>

* 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