<div dir="ltr"><div class="gmail_extra"><br />On Fri, Oct 16, 2015 at 4:12 PM, Robert Haas <<a
href="mailto:robertmhaas@gmail.com">robertmhaas@gmail.com</a>>wrote:<br />><br />> On Fri, Oct 16, 2015 at
6:22AM, Pavel Stehule <<a href="mailto:pavel.stehule@gmail.com">pavel.stehule@gmail.com</a>> wrote:<br />>
>in GoodData we have this feature implemented - little bit different named -<br />> > DROP DATABASE FORCE<br
/>>><br />> > It is useful in complex environment with mix of pooled and not pooled<br />> >
connections- and in our environment - about 2K databases per server with<br />> > lot of dropped / created
databasesper server / per day.<br />> ><br />> > I can publish this patch, if there will be any
interest.<br/>><br />> I think this would be a useful feature. What would one do about<br />> prepared
transactions?<br/>><br /><br /></div><div class="gmail_extra">Isn't "rollback all prepared" before an option?<br
/></div><divclass="gmail_extra"><br /></div><div class="gmail_extra">Regards,<br /></div><div class="gmail_extra"><br
/>--<br/>Fabrízio de Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div></div>
