From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Dan Armbrust" <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "pgsql general" <pgsql-general(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Drop database / database in use question |
Date: | 2008-10-17 16:54:52 |
Message-ID: | dcc563d10810170954m10a2b4aemad079468d8a7a417@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Oct 17, 2008 at 9:16 AM, Dan Armbrust
<daniel(dot)armbrust(dot)list(at)gmail(dot)com> wrote:
> I don't suppose that there is any easy way way that I can stop and/or
> disable the Autovac temporarily for the database that I want to drop.
>
> The only thing that I have seen so far, is that I would have to add
> rows to the pg_autovacuum table for each table in my database, but
> I'm not confident that that would even stop it from accessing the
> database, since it says that even when set to disabled, autovacuum
> will still run to prevent transaction id wraparounds, so it seems that
> it still would make make a quick check into the database that my drop
> command could collide with.
Just set autovacuum = off in postgresql.conf and reload and it's off.
--
When fascism comes to America, it will be draped in a flag and
carrying a cross - Sinclair Lewis
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2008-10-17 17:00:20 | Re: OR or IN ? |
Previous Message | André Volpato | 2008-10-17 16:42:35 | Re: VACUUM PANIC: corrupted item pointer |