From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: DROP DATABASE variant that kills active sessions |
Date: | 2015-10-16 19:34:43 |
Message-ID: | CAFj8pRDBzp1AWCJARFWOwpmjqbTYGqsop4Hr73y2jJY+DMAk_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-10-16 21:12 GMT+02:00 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Fri, Oct 16, 2015 at 6:22 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> > in GoodData we have this feature implemented - little bit different
> named -
> > DROP DATABASE FORCE
> >
> > It is useful in complex environment with mix of pooled and not pooled
> > connections - and in our environment - about 2K databases per server with
> > lot of dropped / created databases per server / per day.
> >
> > I can publish this patch, if there will be any interest.
>
> I think this would be a useful feature. What would one do about
> prepared transactions?
>
It doesn't solve it - GoodData doesn't use it - so I didn't solve this
question - it emulates manual maintenance. In our solution can be some
opened issues.
Patch attached
Regards
Pavel
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
Attachment | Content-Type | Size |
---|---|---|
drop-database-force.patch | text/x-patch | 9.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2015-10-16 19:38:25 | Re: proposal: DROP DATABASE variant that kills active sessions |
Previous Message | Fabrízio de Royes Mello | 2015-10-16 19:32:25 | Re: proposal: DROP DATABASE variant that kills active sessions |