Re: Autovacuum Daemon Disrupting dropdb?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>, PgSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Autovacuum Daemon Disrupting dropdb?
Date: 2006-03-11 22:13:06
Message-ID: 20037.1142115186@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
> I suppose you could instead:

> connect to local postmaster
> disable autovacuum
> pg_dump remotedb
> dropdb localdb
> pg_restore remotedb.pgd
> enable autovacuum

For a "real" solution, perhaps DROP DATABASE could somehow look to
determine if there's an autovac daemon active in the target database,
and if so send it a SIGINT and wait for it to go away.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message venu gopal 2006-03-12 09:12:38 getting failed while creating user accounts
Previous Message Thomas F. O'Connell 2006-03-11 21:01:53 Re: Autovacuum Daemon Disrupting dropdb?