Horton

Re: dropdb --force

Pavel Stehule <pavel.stehule@gmail.com>

View thread View on postgr.es
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Marti Raudsepp <marti@juffo.org>, Filip Rembiałkowski <filip.rembialkowski@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2018-12-19T16:03:41Z
Lists: pgsql-hackers 
st 19. 12. 2018 v 16:55 odesílatel Alvaro Herrera <alvherre@2ndquadrant.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
>

Commits

  1. Add tests for '-f' option in dropdb utility.

  2. Move pump_until to TestLib.pm.

  3. Add the support for '-f' option in dropdb utility.

  4. Introduce the 'force' option for the Drop Database command.

  5. Improve CREATE/DROP/RENAME DATABASE so that when failing because the source