Re: pg_encoding not needed anymore

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_encoding not needed anymore
Date: 2004-04-20 17:37:58
Message-ID: Pine.LNX.4.33.0404201137060.19318-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 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.
>
> Yea, initcluster would have been better, but cluster confuses with
> CLUSTER, just like database schema confuses with CREATE SCHEMA.

Maybe initpg or pg_init or something like that?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2004-04-20 18:19:09 Re: pg_autovacuum crashes when query fails for temp
Previous Message Thomas Swan 2004-04-20 17:29:20 Re: pg_autovacuum crashes when query fails for temp tables