| From: | Halford Dace <hal(at)stowe(dot)co(dot)za> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: VACUUM locking for 21 hours and counting |
| Date: | 2003-03-13 06:53:12 |
| Message-ID: | Pine.SGI.4.44.0303130850170.54536-100000@jove.stowe.co.za |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>
> I run VACUUM.
>
> 21 hours later, I'm still waiting for it to finish.
>
For what it's worth, I sorted this out. Here's the recipe for anyone
stuck in a similar situation. (I'm not sure if it's orthodox or safe, but
it worked today)
1. Stop the postmaster with pg_ctl
2. Send a TERM signal to the nasty postgres process which has been eating
95-99% of one of your CPUs for all the past day.
3. Send TERM signals to any others which suddenly start processing because
they were waiting on locks.
4. Start up as normal with pg_ctl.
5. DROP all teh indices on the table in question
6. VACUUM again - it just takes a couple of minutes.
Am currently busy rebuilding the indices.
Hal
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Rubio | 2003-03-13 07:49:52 | How to compile contribs ... |
| Previous Message | Halford Dace | 2003-03-13 06:22:10 | VACUUM locking for 21 hours and counting |