From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Why does my DB size differ between Production and DR? (Postgres 8.4) |
Date: | 2011-02-01 03:52:08 |
Message-ID: | AANLkTi=PfEAWeOs-Q3HNffX_LM040EdOMt3kAtpJkUDK@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 31, 2011 at 5:54 PM, Aleksey Tsalolikhin
<atsaloli(dot)tech(at)gmail(dot)com> wrote:
> Situation: Disk usage on production server root filesystem is at 68%
> utilization (80 GB used), on DR is at 51% (56 GB used). We use
> SlonyII-1.2.x to keep the DR up to date. I would like to account for
> the 24 GB difference.
This is likely free space in your database. Some of it is completely
normal and actually improves performance. Too much and your db is
bloated and things starting taking too long.
You can reclaim that space by doing a cluster or vacuum full on the
subject table. Setting fill factor ahead of time to something in the
90% range should cut down on bloat as future updates can then happen
in place, and also will improve performance of the system as updates
happen in the same page and if they're not indexed don't require index
updates as well (Heap Only Tuple updates, or HOT updates use this
method)
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Tolley | 2011-02-01 05:40:22 | Re: Automatic database monitoring tool for PostgreSQL ... new project |
Previous Message | Thom Brown | 2011-02-01 02:17:17 | Re: Issues with generate_series using integer boundaries |