From: Jason Earl <jearl@box100.com>
To: eg@tzv.fal.de
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Vacuum takes for ever
Date: Mon, 17 May 1999 12:06:08 -0600
Message-ID: <199905171806.MAA27409@earlj.nesusa.com> (raw)
In-Reply-To: <99051709490504.00692@salo.tzv.fal.de>
References: <99051709490504.00692@salo.tzv.fal.de>
Hello everyone,
in a substantial multi location development project we are using PG
to create a large information system. After having loaded data in
the order of one million records a vaccum took 50h of CPU time on a
350MHz PII (RedHat 5.2, pg 6.4.2). There were no deletes or anyting
like that.
I made a test database when I was deciding whether PostgreSQL was
going to be up to the task. It just so happens that it had a million
records in it as well. The first vacuum took a very very long time,
subsequent vacuums, however, took much less time.
What does vaccum do that takes so long and is there a way to speed
this up?
Apparently it does some "database stuff." Yikes, someone else will
have to answer that question. I just know how to get data in and out
of PostgreSQL.
Jason Earl
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-interfaces@postgresql.org
Cc: jearl@box100.com, eg@tzv.fal.de
Subject: Re: [INTERFACES] Vacuum takes for ever
In-Reply-To: <199905171806.MAA27409@earlj.nesusa.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