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