pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jimn@enterprisedb.com>
To: Kevin Johnson <Kevin.Johnson@noaa.gov>
Cc: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-admin@postgresql.org, Sean Webb <Sean.Webb@noaa.gov>
Subject: Re: Disk space consumed by pk not returned after vacuum or reindex
Date: Fri, 6 Oct 2006 10:37:51 -0500
Message-ID: <8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.com> (raw)
In-Reply-To: <4526326C.2000009@noaa.gov>
References: <45080D4C.2020709@noaa.gov>
	<20060922170557.GB571@wolff.to>
	<452531AB.2050709@noaa.gov>
	<D55BE3CB-D3EF-4089-BFAA-BDD166CD2A5C@enterprisedb.com>
	<4526326C.2000009@noaa.gov>

On Oct 6, 2006, at 5:39 AM, Kevin Johnson wrote:
> You are correct, it is 7.4 we are running on a RHEL3 system.
> The database itself is vacuumed via cron 6 times a day.
>
> Jim Nasby wrote:
>> I didn't see you mention what version you're running; index bloat  
>> shouldn't be a big issue in 7.4 and above. You also didn't mention  
>> how often you're vacuuming the table. If you don't vacuum the  
>> table frequently enough, you're going to get bloat, plain and simple.

For a heavy update load, even 6 times a day may not be enough.

Also, remember that the size you get after a REINDEX will be  
unreasonably low, because there will be very little free space in the  
index. That's fine if you won't be updating the table much, but  
otherwise the index will have no choice but to grow.
--
Jim Nasby                                    jimn@enterprisedb.com
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)





view thread (7+ messages)  latest in thread

Message-ID: <8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.com>
Permalink:  ../8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.com/
Also on:    postgresql.org/message-id/8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jimn@enterprisedb.com, Kevin.Johnson@noaa.gov, bruno@wolff.to, Sean.Webb@noaa.gov
  Subject: Re: Disk space consumed by pk not returned after vacuum or reindex
  In-Reply-To: <8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.com>
  References: <45080D4C.2020709@noaa.gov> <20060922170557.GB571@wolff.to> <452531AB.2050709@noaa.gov> <D55BE3CB-D3EF-4089-BFAA-BDD166CD2A5C@enterprisedb.com> <4526326C.2000009@noaa.gov> <8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.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