From: Bruno Wolff III <bruno@wolff.to>
To: Bealach-na Bo <bealach_na_bo@hotmail.com>
Cc: jnasby@pervasive.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Why so slow?
Date: Fri, 28 Apr 2006 14:00:05 -0500
Message-ID: <20060428190005.GA15689@wolff.to> (raw)
In-Reply-To: <BAY101-F3027DA179AC8CEE9FAAF77ADB20@phx.gbl>
References: <20060428145842.GI97354@pervasive.com>
<BAY101-F3027DA179AC8CEE9FAAF77ADB20@phx.gbl>
On Fri, Apr 28, 2006 at 17:37:30 +0000,
Bealach-na Bo <bealach_na_bo@hotmail.com> wrote:
> >The above shows that the indexes contained 10M rows and 160M of dead
> >space each. That means you weren't vacuuming nearly enough.
>
> How is it that a row in the table can grow to a size far exceeding the sum
> of the maximum sized of the fields it consists of?
Because unless you run vacuum, the old deleted rows are not reused. Those
rows cannot be deleted immediately, because the rows may be visible to
other transactions. Periodic vacuums are used to find deleted rows which
are no longer visible to any transactions.
You probably want to read the following:
http://developer.postgresql.org/docs/postgres/routine-vacuuming.html
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: bruno@wolff.to, bealach_na_bo@hotmail.com, jnasby@pervasive.com
Subject: Re: Why so slow?
In-Reply-To: <20060428190005.GA15689@wolff.to>
* 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