Re: Command tags in create/drop scripts

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Command tags in create/drop scripts
Date: 2007-06-09 01:12:22
Message-ID: 20070609011221.GU92628@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 05, 2007 at 05:52:39PM -0000, Andrew Hammond wrote:
> On Jun 5, 9:19 am, alvhe(dot)(dot)(dot)(at)commandprompt(dot)com (Alvaro Herrera) wrote:
> > Zdenek Kotala wrote:
> > > Tom Lane wrote:
> > > >Bruce Momjian <b(dot)(dot)(dot)(at)momjian(dot)us> writes:
> > > >>Is this a TODO?
> >
> > > >I don't think so; there is no demand from anybody but Zdenek to remove
> > > >those programs. Has it ever even come up before?
> >
> > Personally I found really strange to have "createuser" and "createdb"
> > shipped by Postgres when I started using it. I just didn't complain.
>
> +1. Given the prevalence of the pg_foo convention, those names are
> clunky. So is initdb. I'm less creative than Zdenek, so I'd suggest
> simply renaming to pg_createuser and friends with the same command
> line options as the originals. Have the binaries check $0 and emit a
> warning about using the deprecated name to STDERR if called by a name
> that doesn't have the pg_ prefix. Default to symlinking the old names
> for backwards compatibility until 9.0.

+1
--
Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2007-06-09 01:45:08 Issues with factorial operator
Previous Message Gregory Stark 2007-06-09 00:36:55 Re: Using the GPU