| From: | mkennedy(at)hssinc(dot)com (Matthew Kennedy) |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | strange behaviour |
| Date: | 2000-11-27 17:57:11 |
| Message-ID: | 3A22A077.DF0DAE2B@opushealthcare.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I have a database with a bunch of large tables under postgres 7.0.2
which I've been filling with many rows (order of millions). I have been
copying data into and deleting from frequently. Everything was great
until I upgraded to 7.0.3. Then trying to do _anything_ to that database
via psql caused the postmaster to ram the CPU at 100% indefinitely. I
downgraded to 7.0.2 but I still get this problem.
I know upgrading to 7.0.3 from 7.0.2 shouldn't require a dump/restore...
what could be causing this problem?
--
Matthew Kennedy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nelio Alves Pereira Filho | 2000-11-27 18:00:27 | Re: Trigger question |
| Previous Message | Nick Fankhauser | 2000-11-27 17:41:03 | How to keep Postgres from thrashing for a long time using "LIMIT" (or is there a better way?)! |