From: Tom Lane <tgl@sss.pgh.pa.us>
To: Seum-Lim Gan <slgan@lucent.com>
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 12:42:55 -0400
Message-ID: <4250.1066754575@sss.pgh.pa.us> (raw)
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]>
Seum-Lim Gan <slgan@lucent.com> writes:
> We did a few (like 5 to 8 times) vacuum analyze <tablename> (no full), the
> pg_statistics relfilenode grew.
Well, sure. ANALYZE puts new rows into pg_statistic, and obsoletes old
ones. You need to vacuum pg_statistic every so often (not to mention
the other system catalogs).
> If we do plain simple "vacuum <tablename>" (again no full), we see
> pg_statistics_relid_att_index relfilenode grew instead of
> pg_statistics.
Don't think I believe that. Plain vacuum won't touch pg_statistic
at all (unless it's the target table of course). I'd expect ANALYZE
to make both the stats table and its index grow, though.
regards, tom lane
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: <4250.1066754575@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