Re: [HACKERS] Re: [COMMITTERS] 'postgres95/src/bin/destroydb destroydb.sh' - Mailing list pgsql-hackers

From Igor
Subject Re: [HACKERS] Re: [COMMITTERS] 'postgres95/src/bin/destroydb destroydb.sh'
Date
Msg-id 4e3c2fcb4e958ae353641e46aa37851c
Whole thread Raw
In response to [HACKERS] Re: [COMMITTERS] 'postgres95/src/bin/destroydb destroydb.sh'  (The Hermit Hacker <scrappy@hub.org>)
List pgsql-hackers
Well, rm is also a specific command, yet it's still a good idea to allow
for confirmations...Effects of destroydb are rather permanent ...
The reason I wanted to add this cause I intended to type destroyuser
but accidentally typed destroydb....*sigh* at least I have a backup...
Well...you can still do destroydb -y to force it...maybe building an
environment variable (something like PGFORCEDESTROY or something) would be
ok too...

=+=------------------------/\---------------------------------=+=
       Igor Natanzon      |**|   E-mail: igor@sba.miami.edu
=+=------------------------\/---------------------------------=+=

On Sun, 1 Jun 1997, Thomas G. Lockhart wrote:

> Marc G. Fournier wrote:
> > I am including a patch for destroydb to ask for confirmation before
> > deleting databases (after I accidentally deleted mine)...destroydb -y
> > would force delete without any confirmation.
>
> Uh, "destroydb" would seem to be a specific-enough command that if you
> type it, you actually wanted to delete a database :)
>
> Would have preferred that the behavior remained as-is, myself.
>
>             - Tom
>

------------------------------

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] Protecting macro arguments in dt.h
Next
From: Tymm Twillman
Date:
Subject: Re: [HACKERS] Isn't Purify great? :)