pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Vacuum takes for ever
4+ messages / 4 participants
[nested] [flat]

* Vacuum takes for ever
@ 1999-05-17 07:45 Eildert Groeneveld <eg@tzv.fal.de>
  1999-05-17 18:06 ` Re: [INTERFACES] Vacuum takes for ever Jason Earl <jearl@box100.com>
  1999-05-18 03:24 ` Re: [INTERFACES] Vacuum takes for ever Thomas Lockhart <lockhart@alumni.caltech.edu>
  0 siblings, 2 replies; 4+ messages in thread

From: Eildert Groeneveld @ 1999-05-17 07:45 UTC (permalink / raw)
  To: pgsql-interfaces

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.

What does vaccum do that takes so long and is there a way to speed this up?

greetings


Eildert Groeneveld
=========================================
Institute for
Animal Science and Animal Behaviour
Mariensee 31535 Neustadt Germany
Tel   : (49)(0)5034 871155
Fax   : (49)(0)5034 92579
www   : http://www.tzv.fal.de/~eg/ 
e-mail: eg@tzv.fal.de
=========================================



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: [INTERFACES] Vacuum takes for ever
  1999-05-17 07:45 Vacuum takes for ever Eildert Groeneveld <eg@tzv.fal.de>
@ 1999-05-17 18:06 ` Jason Earl <jearl@box100.com>
  1 sibling, 0 replies; 4+ messages in thread

From: Jason Earl @ 1999-05-17 18:06 UTC (permalink / raw)
  To: eg@tzv.fal.de; +Cc: pgsql-interfaces

   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



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: [INTERFACES] Vacuum takes for ever
  1999-05-17 07:45 Vacuum takes for ever Eildert Groeneveld <eg@tzv.fal.de>
@ 1999-05-18 03:24 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
  1 sibling, 0 replies; 4+ messages in thread

From: Thomas Lockhart @ 1999-05-18 03:24 UTC (permalink / raw)
  To: eg@tzv.fal.de; +Cc: pgsql-interfaces

> What does vaccum do that takes so long and is there a way to speed this up?

Not sure. Try dropping indices if you have any on that table...

                    - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* RE: [INTERFACES] Vacuum takes for ever
@ 1999-05-17 18:45 Jackson, DeJuan <djackson@cpsgroup.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Jackson, DeJuan @ 1999-05-17 18:45 UTC (permalink / raw)
  To: Jason Earl <jearl@box100.com>; eg@tzv.fal.de; +Cc: pgsql-interfaces

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



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~1999-05-18 03:24 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-05-17 07:45 Vacuum takes for ever Eildert Groeneveld <eg@tzv.fal.de>
1999-05-17 18:06 ` Jason Earl <jearl@box100.com>
1999-05-18 03:24 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
1999-05-17 18:45 RE: [INTERFACES] Vacuum takes for ever Jackson, DeJuan <djackson@cpsgroup.com>

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