pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shane Ambler <pgsql@Sheeky.Biz>
To: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: Andrew Sullivan <ajs@commandprompt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Tue, 29 Apr 2008 20:49:38 +0930
Message-ID: <4817044A.6000800@Sheeky.Biz> (raw)
In-Reply-To: <7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
	<a2de01dd0804280658t68ac22dsf182d304a94de5a2@mail.gmail.com>
	<7e4ba9550804280705q43c51e66l104a5ff9272bbd4d@mail.gmail.com>
	<20080428162243.GN2970@commandprompt.com>
	<7e4ba9550804282246p73c62fc6y5e7cb7dda55a6b50@mail.gmail.com>

Gauri Kanekar wrote:
> Andrew,
> 
> Can you explain me in detail why u said vacuum full is making the things
> worst.
> We do vacuum full, as vacuum verbose analyse dont regain space for us.
> 

vacuum full stops all access so that the data files can be re-writen 
without the unused space.

normal vacuum will update the records of what space is no longer used so 
that it can then be reused with the next update/insert. Your db size 
will not shrink straight away but it will stop growing until you use all 
the free space left from previous update/delete

The more frequently you do a normal vacuum the less time it will take 
and things will run a lot smoother with your file size growing slowly to 
accommodate new data.

Expanding on what others have mentioned as a drawback of vacuum full - 
you should look at REINDEX'ing as well (maybe one index or table at a 
time). You will most likely find this will reclaim some disk space for 
you as well.




-- 

Shane Ambler
pgSQL (at) Sheeky (dot) Biz

Get Sheeky @ http://Sheeky.Biz



view thread (48+ messages)  latest in thread

Message-ID: <4817044A.6000800@Sheeky.Biz>
Permalink:  ../4817044A.6000800@Sheeky.Biz/
Also on:    postgresql.org/message-id/4817044A.6000800@Sheeky.Biz

 · 

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: pgsql@Sheeky.Biz, meetgaurikanekar@gmail.com, ajs@commandprompt.com
  Subject: Re: Replication Syatem
  In-Reply-To: <4817044A.6000800@Sheeky.Biz>

* 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