Re: Problem Dropping a Database with users connected to it
От | Eric Dorland |
---|---|
Тема | Re: Problem Dropping a Database with users connected to it |
Дата | |
Msg-id | 1105736359.7029.28.camel@garuda.wcg.mcgill.ca обсуждение исходный текст |
Ответ на | Re: Problem Dropping a Database with users connected to it (Bruno Wolff III <bruno@wolff.to>) |
Список | pgsql-general |
On Fri, 2005-01-14 at 10:58 -0600, Bruno Wolff III wrote: > On Fri, Jan 14, 2005 at 11:16:16 -0500, > Eric Dorland <eric.dorland@mcgill.ca> wrote: > > > > * Disconnecting all other users before dropping the db, but that doesn't > > seem possible (I could start and stop the db, but that doesn't stop any > > clients from just reconnecting right away). > > You could use an alter pg_hba.conf file while doing the drop. > > > * Just drop all the tables, etc. instead of dropping the db. There > > doesn't seem to be a good way to do this except doing an explicit DROP > > TABLE foo on all 200 tables. Is there a good recipe for this, an easy > > way to get a listing of all the tables in a db? > > If all of the tables are in the public schema, dropping that schema should > cascade to dropping all of the tables. I had not considered dropping the schema, but that sounds like a good solution. I'll give it a shot. -- Eric Dorland eric.dorland@mcgill.ca WCG 514.398-5023 ext. 09562
В списке pgsql-general по дате отправления: