On Tuesday 20 April 2004 16:54, Andrew Dunstan wrote:
Joshua D. Drake wrote:
g a data store for many databases, not a single database. But I
think it is far too sanctified by history to change now, just as Ken
Thompson now wishes he had put an 'e' on the end of 'creat' but can't
go back
On Mon, Apr 19, 2004 at 08:41:18PM -0400, Bruce Momjian wrote:
With initdb written now in C, we don't need a pg_encoding binary
anymore.
By the way, what change the name of initdb to pg_initdb. The
current name is really too common (like some others things in
pgsql/src/bin)
Karel Zak wrote:
On Mon, Apr 19, 2004 at 08:41:18PM -0400, Bruce Momjian wrote:
With initdb written now in C, we don't need a pg_encoding binary
anymore.
By the way, what change the name of initdb to pg_initdb. The
current name is really too common (like some others
On Tue, Apr 20, 2004 at 08:59:20AM -0400, Bruce Momjian wrote:
Karel Zak wrote:
On Mon, Apr 19, 2004 at 08:41:18PM -0400, Bruce Momjian wrote:
With initdb written now in C, we don't need a pg_encoding binary
anymore.
By the way, what change the name of initdb to pg_initdb.
Bruce Momjian wrote:
Karel Zak wrote:
On Mon, Apr 19, 2004 at 08:41:18PM -0400, Bruce Momjian wrote:
With initdb written now in C, we don't need a pg_encoding binary
anymore.
By the way, what change the name of initdb to pg_initdb. The
current name is really too common
Andrew Dunstan wrote:
past. I think createuser is much worse. :-)
Agreed. Actually, the big problem with the name initdb is that the
name is misleading, and newbies often get confused by it. You are
preparing a data store for many databases, not a single database. But I
think it
Joshua D. Drake wrote:
g a data store for many databases, not a single database. But I
think it is far too sanctified by history to change now, just as Ken
Thompson now wishes he had put an 'e' on the end of 'creat' but can't
go back and fix it. Maybe we should think about a symlink/hardlink
g a data store for many databases, not a single database. But I think
it is far too sanctified by history to change now, just as Ken
Thompson now wishes he had put an 'e' on the end of 'creat' but can't
go back and fix it. Maybe we should think about a symlink/hardlink to
use a better name.
On Tue, 20 Apr 2004, Bruce Momjian wrote:
Andrew Dunstan wrote:
past. I think createuser is much worse. :-)
Agreed. Actually, the big problem with the name initdb is that the
name is misleading, and newbies often get confused by it. You are
preparing a data store for many
