Received: from bjke.com (firewall-user@ganymede.bjke.com [144.210.8.38]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA15358 for ; Mon, 17 May 1999 14:45:47 -0400 (EDT) (envelope-from djackson@cpsgroup.com) Received: by bjke.com; id NAA15747; Mon, 17 May 1999 13:45:44 -0500 (CDT) Received: from unknown(144.210.12.10) by gauntlet.bjke.com via smap (4.1) id xma015360; Mon, 17 May 99 13:44:55 -0500 Received: by cpsmail with Internet Mail Service (5.5.2448.0) id ; Mon, 17 May 1999 13:45:15 -0500 Message-ID: From: "Jackson, DeJuan" To: Jason Earl , 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 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain 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