| From: | "Tony Wasson" <ajwasson(at)gmail(dot)com> |
|---|---|
| To: | jim(at)contactbda(dot)com |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: drop database command blocking other connections |
| Date: | 2006-05-03 21:09:05 |
| Message-ID: | 6d8daee30605031409g597710acue5eabcefeed4f964@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/3/06, Jim Buttafuoco <jim(at)contactbda(dot)com> wrote:
> from time to time I have to drop a very large database (1TB+). The drop database command takes a long time to complete
> while its deleting the files. During this time, no one can connect to the database server, ps displays "startup
> waiting". This is with Postgresql 7.4. Has this been addressed in 8.1, if not, does anyone have some ideas on how to
> speed this up.
I don't have a "fix", but I can offer a workaround.
When we need to drop large DBs we drop them a schema at a time. DROP
SCHEMA does *not* block new connections into the server. Once the data
it out of the schema(s), a DROP DATABASE on a nearly empty database
does not block new connections for more than a moment.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Buttafuoco | 2006-05-03 21:18:24 | Re: drop database command blocking other connections |
| Previous Message | Jonah H. Harris | 2006-05-03 20:23:59 | Re: [SoC] Relation between project "XML improvements" and "pgxml" |