From: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: serious problems with vacuuming databases
Date: Sun, 09 Apr 2006 22:44:51 +0200
Message-ID: <44397243.6010208@fuzzy.cz> (raw)
In-Reply-To: <44397071.80008@fuzzy.cz>
References: <443950FB.4050707@fuzzy.cz>
<20060409183747.GB15094@surnet.cl>
<44397071.80008@fuzzy.cz>
> I guess you're right. I forgot to mention there are 12 composed indexes
> on the largest (and not deleted) table B, having about 14.000.000 rows
> and 1 GB of data. I'll try to dump/reload the database ...
Aaargh, the problem probably is not caused by the largest table, as it
was dropped, filled in with the data and after that all the indexes were
created. The problem could be caused by the tables with deleted data, of
course.
t.v.
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: tv@fuzzy.cz
Subject: Re: serious problems with vacuuming databases
In-Reply-To: <44397243.6010208@fuzzy.cz>
* 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