From: hubert depesz lubaczewski <depesz@gmail.com>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: PostgreSQL General <pgsql-general@postgresql.org>
Cc: pgsqlperform <pgsql-performance@postgresql.org>
Subject: Re: database bloat, but vacuums are done, and fsm seems to be setup ok
Date: Sat, 1 Oct 2005 12:01:04 +0200
Message-ID: <9e4684ce0510010301ibfafcb2l10e5344b798433b4@mail.gmail.com> (raw)
In-Reply-To: <20050930193459.GC40138@pervasive.com>
References: <9e4684ce05092800075d37d0cc@mail.gmail.com>
<20050930193459.GC40138@pervasive.com>
On 9/30/05, Jim C. Nasby <jnasby@pervasive.com> wrote:
>
> Looks like it's definately an issue with index bloat. Note that it's
> normal to have some amount of empty space depending on vacuum and update
> frequency, so 15G -> 20G isn't terribly surprising. I would suggest
> using pg_autovacuum instead of the continuous vacuum; it's very possible
> that some of your tables need more frequent vacuuming than they're
> getting now. If you go this route, you might want to change the default
> settings a bit to make pg_autovacuum more agressive.
actually i have a very bad experience with autovaccum - of course it is
because i dont know how to setup it correctly, but for me it's just easier
to setup continuos vacuums. and i know which tables are frequently updated,
so i setup additional vacuums on them.
Also, I'd suggest posting to -hackers about the index bloat. Would you
> be able to make a filesystem copy (ie: tar -cjf database.tar.bz2
> $PGDATA) available? It might also be useful to keep an eye on index size
> in pg_class.relpages and see exactly what indexes are bloating.
i'm watching it right now (which indices are bloating), but i cannot send
copy of pgdata - it contains very sensitive information.
depesz
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: depesz@gmail.com, jnasby@pervasive.com, pgsql-general@postgresql.org
Subject: Re: database bloat, but vacuums are done, and fsm seems to be setup ok
In-Reply-To: <9e4684ce0510010301ibfafcb2l10e5344b798433b4@mail.gmail.com>
* 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