pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rafael Martinez <r.m.guerrero@usit.uio.no>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Need to run CLUSTER to keep performance
Date: Thu, 08 Nov 2007 16:15:45 +0100
Message-ID: <47332821.3010505@usit.uio.no> (raw)
In-Reply-To: <473326C3.3070206@enterprisedb.com>
References: <4732E6B4.1030907@usit.uio.no>
	<4732EF07.3060807@enterprisedb.com>
	<47332200.9050705@usit.uio.no>
	<473326C3.3070206@enterprisedb.com>

Heikki Linnakangas wrote:
>
> If the table is already bloated, a VACUUM won't usually shrink it. It
> only makes the space available for reuse, but a sequential scan still
> needs to go through a lot of pages.
> 
> CLUSTER on the other hand repacks the tuples and gets rid of all the
> unused space on pages. You need to run CLUSTER or VACUUM FULL once to
> shrink the relation, but after that frequent-enough VACUUMs should keep
> the table size down.
> 

Ok, thanks for the advice. We will try this and will come back with more
information.

-- 
 Rafael Martinez, <r.m.guerrero@usit.uio.no>
 Center for Information Technology Services
 University of Oslo, Norway

 PGP Public Key: http://folk.uio.no/rafael/



view thread (21+ messages)  latest in thread

Message-ID: <47332821.3010505@usit.uio.no>
Permalink:  ../47332821.3010505@usit.uio.no/
Also on:    postgresql.org/message-id/47332821.3010505@usit.uio.no

 · 

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: r.m.guerrero@usit.uio.no, heikki@enterprisedb.com
  Subject: Re: Need to run CLUSTER to keep performance
  In-Reply-To: <47332821.3010505@usit.uio.no>

* 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