pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Correction - not crash
2+ messages / 2 participants
[nested] [flat]

* Correction - not crash
@ 1999-03-04 13:26 Tim Perdue <perdue@raccoon.com>
  1999-03-04 15:11 ` Re: [SQL] Correction - not crash G. Anthony Reina <reina@nsi.edu>
  0 siblings, 1 reply; 2+ messages in thread

From: Tim Perdue @ 1999-03-04 13:26 UTC (permalink / raw)
  To: pgsql-sql@hub.org

I have to correct my prior message. Postgres isn't crashing during vacuums -
the vacuums are just going on indefinitely, eating 100% CPU.

I tried manually issuing the vacuum command and it did the same thing...




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

* Re: [SQL] Correction - not crash
  1999-03-04 13:26 Correction - not crash Tim Perdue <perdue@raccoon.com>
@ 1999-03-04 15:11 ` G. Anthony Reina <reina@nsi.edu>
  0 siblings, 0 replies; 2+ messages in thread

From: G. Anthony Reina @ 1999-03-04 15:11 UTC (permalink / raw)
  To: Tim Perdue <perdue@raccoon.com>; +Cc: pgsql-sql@hub.org

Tim,

    It sounds like one of your table indicies became corrupted. I had a
similar thing happen to me before. To test this, try vacuuming each
table separately (i.e. 'vacuum verbose analyze tablename'). If each
table vacuums separately, then it is a problem with the main index (the
table of tables). In this case, you'll probably have to pg_dump and
restore the database (or possibly first try to drop the indicies and
re-create them).

-Tony





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


end of thread, other threads:[~1999-03-04 15:11 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-03-04 13:26 Correction - not crash Tim Perdue <perdue@raccoon.com>
1999-03-04 15:11 ` G. Anthony Reina <reina@nsi.edu>

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