pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Hoover <revoohc@sermonaudio.com>
To: pgsql-admin@postgresql.org
Subject: Vacuum questions
Date: Tue, 15 Mar 2005 15:46:57 -0500
Message-ID: <423749C1.2030803@sermonaudio.com> (raw)

Question on vacuuming.

When you do a vacuum <table>, are the "freed" tuples available only the 
table, or to the entire db, or to the entire cluster?

The reason I'm asking is that we are getting ready to preform a major 
upgrade to our application that involves adding some new fields to 
almost every table and populating them.  This is causing our test 
conversion db's to double in size (we are assuming that every update is 
causing a delete and re-insert behind the scenes due to the populating 
of the new columns).  Anyway, we are working on trying to find the 
fastest way to recover the space.

We have also had one test occurrence where after the upgrade, a vacuum 
full would not recover the space.  However, when we bounced the 
postmaster, and then performed a vacuum full, the space was recovered.  
Any ideas on what might cause this?  This happened on a newly restored 
db that was converted and then vacuumed full.  There would have been no 
connections to the db after the conversion.

PG 7.3.4
RH 2.1

Thanks,

Chris




view thread (6+ messages)  latest in thread

Message-ID: <423749C1.2030803@sermonaudio.com>
Permalink:  ../423749C1.2030803@sermonaudio.com/
Also on:    postgresql.org/message-id/423749C1.2030803@sermonaudio.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-admin@postgresql.org
  Cc: revoohc@sermonaudio.com
  Subject: Re: Vacuum questions
  In-Reply-To: <423749C1.2030803@sermonaudio.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