From: Seum-Lim Gan <slgan@lucent.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: index file bloating still in 7.4 ?
Date: Tue, 21 Oct 2003 11:25:33 -0500
Message-ID: <p05100321bbbb0a94a8c7@[192.168.10.52]> (raw)
In-Reply-To: <15841.1066685113@sss.pgh.pa.us>
References: <p0510030cbbb7667a7f87@[192.168.10.52]>
<19692.1066578442@sss.pgh.pa.us>
<p05100318bbb86e62801a@[192.168.10.52]>
<200310191204.23888.josh@agliodbs.com>
<p05100307bbb9b21e995f@[192.168.10.52]>
<p0510030cbbb9ff79c606@[192.168.10.52]>
<15841.1066685113@sss.pgh.pa.us>
Hi Tom,
1.)
OK. We have narrowed it down.
We did a few (like 5 to 8 times) vacuum analyze <tablename> (no full), the
pg_statistics relfilenode grew. There was no database operation when
we did this, no other client connections except the one that does
the vacuum.
If we do plain simple "vacuum <tablename>" (again no full), we see
pg_statistics_relid_att_index relfilenode grew instead of
pg_statistics.
So, overtime, these files will grow if we do vacuum.
Are these expected ?
The question now is, if we are not doing anything
to the database, why would they grow after a few vacuums ?
2.)
The other problem we have with
> DETAIL: 101802 dead row versions cannot be removed yet.
> DETAIL: 110900 dead row versions cannot be removed yet.
> DETAIL: 753064 dead row versions cannot be removed yet.
> DETAIL: 765328 dead row versions cannot be removed yet.
We will collect more data and see what we can get from the
the process. Offhand, the process is connecting to
the database through ODBC and we don't use any BEGIN in
our updates, just doing plain UPDATE repeatedly
with different keys randomly.
The database is defaulted to autocommit=true in postgresql.conf.
Thanks.
Gan
At 5:25 pm -0400 2003/10/20, Tom Lane wrote:
>Seum-Lim Gan <slgan@lucent.com> writes:
>> We tried one more thing: with the table not being updated
>> at all and we did vacuum. Each time a vacuum is done,
>> the index file becomes bigger.
>
>It is not possible for plain vacuum to make the index bigger.
>
>VACUUM FULL possibly could make the index bigger, since it has to
>transiently create duplicate index entries for every row it moves.
>
>If you want any really useful comments on your situation, you're going
>to have to offer considerably more detail than you have done so far ---
>preferably, a test case that lets someone else reproduce your results.
>So far, all we can do is guess on the basis of very incomplete
>information. When you aren't even bothering to mention whether a vacuum
>is FULL or not, I have to wonder whether I have any realistic picture of
>what's going on.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
--
+--------------------------------------------------------+
| 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 |
+--------------------------------------------------------+
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: <p05100321bbbb0a94a8c7@[192.168.10.52]>
References: <p0510030cbbb7667a7f87@[192.168.10.52]> <19692.1066578442@sss.pgh.pa.us> <p05100318bbb86e62801a@[192.168.10.52]> <200310191204.23888.josh@agliodbs.com> <p05100307bbb9b21e995f@[192.168.10.52]> <p0510030cbbb9ff79c606@[192.168.10.52]> <15841.1066685113@sss.pgh.pa.us> <p05100321bbbb0a94a8c7@[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