Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203])
	by hub.org (8.9.3/8.9.3) with ESMTP id LAA31570
	for <pgsql-hackers@postgreSQL.org>;
	Tue, 21 Sep 1999 11:22:13 -0400 (EDT)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1])
	by localhost (8.8.7/8.8.7) with ESMTP id PAA15318;
	Tue, 21 Sep 1999 15:21:32 GMT
Sender: lockhart@hub.org
Message-ID: <37E7A27B.6BF226AD@alumni.caltech.edu>
Date: Tue, 21 Sep 1999 15:21:31 +0000
From: Thomas Lockhart <lockhart@alumni.caltech.edu>
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Momjian <maillist@candle.pha.pa.us>
CC: The Hermit Hacker <scrappy@hub.org>,
	PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: [HACKERS] Re: HISTORY for 6.5.2]
References: <199909211452.KAA11058@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> > Or have the createdb command run 'man createdb' *grin*
> I was thinking:
>         See the CREATE DATABASE command for more options.

I can't help thinking that this thread is trying to solve a problem
that isn't a problem. createdb works fine. You can do more from within
sql. So what? Someone could, if they thought it was a problem, add
more capabilities to createdb, and an admin could choose to use it or
not.

Seems to me that it works just fine for most cases right now; sure
does for me...

                      - Thomas

-- 
Thomas Lockhart				lockhart@alumni.caltech.edu
South Pasadena, California