pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Seum-Lim Gan <slgan@lucent.com>
Cc: josh@agliodbs.com
Cc: pgsql-performance@postgresql.org
Subject: Re: index file bloating still in 7.4 ?
Date: Sat, 18 Oct 2003 22:21:00 -0400
Message-ID: <16213.1066530060@sss.pgh.pa.us> (raw)
In-Reply-To: <p0510030dbbb79c742da5@[192.168.10.52]>
References: <p0510030cbbb7667a7f87@[192.168.10.52]>
	<200310181458.15575.josh@agliodbs.com>
	<p0510030dbbb79c742da5@[192.168.10.52]>

Seum-Lim Gan <slgan@lucent.com> writes:
> Sample verbose analyze:

> VACUUM VERBOSE ANALYZE hello_rda_or_key;
> INFO:  vacuuming "craft.hello_rda_or_key"
> INFO:  index "hello242_1105" now contains 740813 row versions in 2477 pages

So what's the problem?  That doesn't seem like a particularly bloated
index.  You didn't say what datatype the index is on, but making the
most optimistic assumptions, index entries must use at least 16 bytes
each.  You're getting about 300 entries per page, compared to the
theoretical limit of 512 ... actually more, since I'm not allowing for
upper btree levels in this calculation ... which says to me that the
page loading is right around the expected btree loading of 2/3.

			regards, tom lane



view thread (18+ messages)  latest in thread

Message-ID: <16213.1066530060@sss.pgh.pa.us>
Permalink:  ../16213.1066530060@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16213.1066530060@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, slgan@lucent.com, josh@agliodbs.com
  Subject: Re: index file bloating still in 7.4 ?
  In-Reply-To: <16213.1066530060@sss.pgh.pa.us>

* 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