| From: | "Robert M(dot) Meyer" <rmeyer(at)installs(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | What to do about a vacuum... |
| Date: | 2002-08-09 13:24:32 |
| Message-ID: | 1028899472.28130.4.camel@skymaster |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
IN my infinite wisdom, in an effort to resolve my performance problems,
I started a full vacuum of my database last night around 4:00AM. It's
still running at 9;20AM and it has all of the tables locked. Is it safe
to cancel the query from inside pgmonitor? I've pretty much determined
that ripping the thread out by the roots is a bad thing.
This goes back to my earlier thread about postgres performance slowly
getting worse. I made the assumption that we were doing full vacuums
knew for sure. I checked the script yesterday and found that the '-f'
flag was not turned on...so I turned it on.
It has gotten to the part where it pegs the CPU (99.9% of one cpu) and
it's been there for a while. So far, it's rung up 3:13 of CPU time
since it started.
Can I cancel the query and what will that do to me?
Thanks...
Cheers!
Bob
--
Robert M. Meyer
Sr. Network Administrator
DigiVision Satellite Services
14 Lafayette Sq, Ste 410
Buffalo, NY 14203-1904
(716)332-1451
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-09 13:47:18 | Re: What to do about a vacuum... |
| Previous Message | Geoff | 2002-08-09 10:32:05 | problem with select into and timestamp. |