Re: dropdb --force

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Marti Raudsepp <marti(at)juffo(dot)org>, Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: dropdb --force
Date: 2018-12-19 16:03:41
Message-ID: CAFj8pRDSmF5tPx8SywJW6Qe5C7fBEeu0kp7mzq69uxyA7etLTA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

st 19. 12. 2018 v 16:55 odesílatel Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
napsal:

> I wonder if this idea from seven years ago might be useful:
> https://postgr.es/m/1305688547-sup-7028@alvh.no-ip.org

Why not - I see this as little bit different case - when I used drop
database force than I didn't need to wait on clients.

The target is clean, but the methods can be different due different
environments, goals and sensitivity

>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2018-12-19 16:38:00 Re: Remove Deprecated Exclusive Backup Mode
Previous Message Alvaro Herrera 2018-12-19 15:55:30 Re: dropdb --force