pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jackson, DeJuan <djackson@cpsgroup.com>
To: 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 13:45:15 -0500
Message-ID: <D05EF808F2DFD211AE4A00105AA1B5D216F043@cpsmail> (raw)

vacuum - adjusts the rows in a disk file (it might do more)
vacuum analyze - does the above and updates the table's statistics for
planning
	-DEJ
>    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



view thread (4+ messages)  latest in thread

Message-ID: <D05EF808F2DFD211AE4A00105AA1B5D216F043@cpsmail>
Permalink:  ../D05EF808F2DFD211AE4A00105AA1B5D216F043@cpsmail/
Also on:    postgresql.org/message-id/D05EF808F2DFD211AE4A00105AA1B5D216F043@cpsmail

 · 

reply

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: djackson@cpsgroup.com, jearl@box100.com, eg@tzv.fal.de
  Subject: RE: [INTERFACES] Vacuum takes for ever
  In-Reply-To: <D05EF808F2DFD211AE4A00105AA1B5D216F043@cpsmail>

* 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