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

Hi Tom,

I did that when I have stopped my updates.

Now, I am doing updates below is the output of vacuum.
After doing the vacuum verbose analyze, it reported the following :

INFO:  vacuuming "craft.dsperf_rda_or_key"
INFO:  index "hello242_1105" now contains 1792276 row versions in 6237 pages
DETAIL:  0 index pages have been deleted, 0 are currently reusable.
CPU 0.61s/0.36u sec elapsed 17.92 sec.
INFO:  "hello_rda_or_key": found 0 removable, 1791736 nonremovable 
row versions in 30892 pages
DETAIL:  1492218 dead row versions cannot be removed yet.
There were 0 unused item pointers.
0 pages are entirely empty.
CPU 1.95s/1.99u sec elapsed 26.95 sec.
INFO:  analyzing "craft.dsperf_rda_or_key"
INFO:  "hello_rda_or_key": 30909 pages, 3000 rows sampled, 93292 
estimated total rows
VACUUM

Gan

At 10:21 pm -0400 2003/10/18, Tom Lane wrote:
>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


-- 
+--------------------------------------------------------+
| Seum-Lim GAN                 email : slgan@lucent.com  |
| Lucent Technologies                                    |
| 2000 N. Naperville Road, 6B-403F  tel : (630)-713-6665 |
| Naperville, IL 60566, USA.        fax : (630)-713-7272 |
|       web : http://inuweb.ih.lucent.com/~slgan         |
+--------------------------------------------------------+



view thread (18+ messages)  latest in thread

Message-ID: <p0510030ebbb7cabb0ceb@[192.168.10.52]>
Permalink:  ../p0510030ebbb7cabb0ceb@%5B192.168.10.52%5D/
Also on:    postgresql.org/message-id/p0510030ebbb7cabb0ceb@[192.168.10.52]

 · 

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-performance@postgresql.org
  Cc: slgan@lucent.com, tgl@sss.pgh.pa.us, josh@agliodbs.com
  Subject: Re: index file bloating still in 7.4 ?
  In-Reply-To: <p0510030ebbb7cabb0ceb@[192.168.10.52]>
  References: <p0510030cbbb7667a7f87@[192.168.10.52]> <200310181458.15575.josh@agliodbs.com> <p0510030dbbb79c742da5@[192.168.10.52]> <16213.1066530060@sss.pgh.pa.us> <p0510030ebbb7cabb0ceb@[192.168.10.52]>

* 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