pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: bangh <banghe@baileylink.net>
To: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Vacuum
Date: Thu, 29 Nov 2001 10:06:02 -0600
Message-ID: <3C065CEA.B23D9745@baileylink.net> (raw)
References: <20011127085555.A20745-100000@megazone23.bigpanda.com>
	<3C04A23E.BF409D74@answare.fr>
	<2131.1006960265@sss.pgh.pa.us>
	<3C0510FF.694D34EA@answare.fr>
	<2528.1006965329@sss.pgh.pa.us>
	<3C051482.908DEDFF@answare.fr>
	<2775.1006967609@sss.pgh.pa.us>
	<3C05F979.ED76D96D@answare.fr>
	<18157.1007043873@sss.pgh.pa.us>
	<18448.1007046370@sss.pgh.pa.us>

Hello,

Using vacuum a table is very usefull to compress the space of a table .
However I noticed the index grows also very fast. Does anyone have a way to
compress the index? I know if I dump the  database, and destroy the orginal
database, then create new one using the same database, and restory the dump
file, that will dramatically compress the space the database has taken. This
is not a good way for a live database that is driven by the web application
that means I have to shut down the web application service during this
clearup.

Thanks,

Bangh




view thread (33+ messages)  latest in thread

Message-ID: <3C065CEA.B23D9745@baileylink.net>
Permalink:  ../3C065CEA.B23D9745@baileylink.net/
Also on:    postgresql.org/message-id/3C065CEA.B23D9745@baileylink.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-admin@postgresql.org
  Cc: banghe@baileylink.net
  Subject: Re: Vacuum
  In-Reply-To: <3C065CEA.B23D9745@baileylink.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