| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | salah jubeh <s_jubeh(at)yahoo(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add force option to dropdb |
| Date: | 2014-01-14 19:06:44 |
| Message-ID: | 20140114190644.GI6840@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
salah jubeh wrote:
> For the sake of completeness:
> 1. I think also, I need also to temporary disallow conecting to the database, is that right?
> 2. Is there other factors can hinder dropping database?
If the user owns objects, that will prevent this from working also. I
have the feeling that adding DROP OWNED BY and/or REASSIGNED OWNED BY
calls to this utility would be a bit excessive, but who knows.
> 3. Should I write two patches one for pg_version>=9.2 and one for pg_version<9.2
No point -- nothing gets applied to branches older than current
development anyway.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-01-14 19:07:30 | Re: GIN improvements part2: fast scan |
| Previous Message | Gavin Flower | 2014-01-14 19:03:28 | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |