Re: proposal: DROP DATABASE variant that kills active sessions - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: proposal: DROP DATABASE variant that kills active sessions
Date
Msg-id CAFcNs+ohbPpjSn+t81W2UnewOe2mh+FTa2o5fs3tK1RsE+Y_OA@mail.gmail.com
Whole thread
In response to Re: proposal: DROP DATABASE variant that kills active sessions  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: proposal: DROP DATABASE variant that kills active sessions
List pgsql-hackers

On Fri, Oct 16, 2015 at 4:12 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Fri, Oct 16, 2015 at 6:22 AM, Pavel Stehule <pavel.stehule@gmail.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?
>

Isn't "rollback all prepared" before an option?

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: remaining open items
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: DROP DATABASE variant that kills active sessions