| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daniel Migowski <dmigowski(at)ikoffice(dot)de> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Cannot drop database because of AUTOVACUUM |
| Date: | 2011-12-24 14:39:37 |
| Message-ID: | 13480.1324737577@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Daniel Migowski <dmigowski(at)ikoffice(dot)de> writes:
> I have a rare problem. I just restored a large database, and found out I made an error. Now I want to drop it, but can't do it because of the autovacuum process, running for minutes now, which i don't want to kill.
Um ... if you're going to drop the database, why would you care about
letting an autovacuum complete? Its work would only be thrown away
anyway.
> Isn't it possible to stop it from running if this is the only process connected to a database when I want to drop it?
An autovacuum process should get killed automatically if you issue a
DROP against its database (or table, for that matter).
If there's a bug here, you've not explained what it is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | stef.couston | 2011-12-24 15:48:33 | BUG #6357: cant download |
| Previous Message | Daniel Migowski | 2011-12-24 12:06:25 | Cannot drop database because of AUTOVACUUM |