Skip site navigation (1) Skip section navigation (2)

Re: Command tags in create/drop scripts

From: Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Command tags in create/drop scripts
Date: 2007-06-05 17:52:39
Message-ID: 1181065959.618700.42900@j4g2000prf.googlegroups.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

Andrew


In response to

Responses

pgsql-hackers by date

Next:From: Chander GanesanDate: 2007-06-05 19:29:14
Subject: Re: CREATEROLE, CREATEDB
Previous:From: Tom LaneDate: 2007-06-05 17:02:28
Subject: Re: Implicit casts with generic arrays

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group