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

help / color / mirror / Atom feed
From: Alan Stange <stange@rentec.com>
To: Vivek Khera <vivek@khera.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: postgresql performance tuning
Date: Tue, 06 Dec 2005 15:48:20 -0500
Message-ID: <4395F914.8070001@rentec.com> (raw)
In-Reply-To: <F069CC64-C748-4EC1-ADF3-38D2FBC230CD@khera.org>
References: <Pine.LNX.4.58.0512060941090.21795@karadi.cs.wisc.edu>
	<F069CC64-C748-4EC1-ADF3-38D2FBC230CD@khera.org>

Vivek Khera wrote:
>
> On Dec 6, 2005, at 11:14 AM, Ameet Kini wrote:
>
>> need for vacuums. However, it'd be great if there was a similar 
>> automatic
>> reindex utility, like say, a pg_autoreindex daemon. Are there any plans
>> for this feature?  If not, then would cron scripts be the next best
>
> what evidence do you have that you are suffering index bloat?  or are 
> you just looking for solutions to problems that don't exist as an 
> academic exercise? :-) 

The files for the two indices on a single table used 7.8GB of space 
before a reindex, and 4.4GB after.   The table had been reindexed over 
the weekend and a vacuum was completed on the table about 2 hours ago.

The two indices are now 3.4GB smaller.   I don't think this counts as 
bloat, because of our use case.  Even so, we reindex our whole database 
every weekend.

-- Alan




view thread (18+ messages)  latest in thread

Message-ID: <4395F914.8070001@rentec.com>
Permalink:  ../4395F914.8070001@rentec.com/
Also on:    postgresql.org/message-id/4395F914.8070001@rentec.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-performance@postgresql.org
  Cc: stange@rentec.com, vivek@khera.org
  Subject: Re: postgresql performance tuning
  In-Reply-To: <4395F914.8070001@rentec.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