Re: Autovacuum Daemon Disrupting dropdb? - Mailing list pgsql-general

From Tom Lane
Subject Re: Autovacuum Daemon Disrupting dropdb?
Date
Msg-id 20037.1142115186@sss.pgh.pa.us
Whole thread Raw
In response to Re: Autovacuum Daemon Disrupting dropdb?  ("Matthew T. O'Connor" <matthew@zeut.net>)
Responses Re: Autovacuum Daemon Disrupting dropdb?  ("Thomas F. O'Connell" <tfo@sitening.com>)
List pgsql-general
"Matthew T. O'Connor" <matthew@zeut.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

pgsql-general by date:

Previous
From: "Thomas F. O'Connell"
Date:
Subject: Re: Autovacuum Daemon Disrupting dropdb?
Next
From: venu gopal
Date:
Subject: getting failed while creating user accounts