| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(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:12:07 |
| Message-ID: | CA+TgmobWB6tdy5d_4c4SrHuM7RKBaWBKZGiEntCMjrd+MaP2Pg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-10-16 19:14:24 | Re: remaining open items |
| Previous Message | Robert Haas | 2015-10-16 19:10:31 | Re: Foreign join pushdown vs EvalPlanQual |