Re: script binaries renaming

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Dave Page <dpage(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: script binaries renaming
Date: 2007-07-07 18:50:29
Message-ID: 6227.1183834229@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Dave Page wrote:
>> This is almost as bad as Magnus agreeing with JD (!), but I agree with
>> Peter :-). After years of typing the current names, changing them does
>> seem somewhat annoying. Worse yet, pg_* is just awkward to type.

> But these utilities are mostly using in scripts -> one type, multi use.

According to whom? The ones that are really at issue I think are
createuser/createlang/dropuser/droplang, and those seem mainly intended
for interactive use. In a script you might as well use psql -c.

The ones that have "db" in the name do not seem to me to need renaming.
While maybe not obviously connected to Postgres, the chance of a
collision with some other project is low.

One that I'd personally vote to remove completely is "ipcclean".
It's always been a crude, incomplete hack anyway, and the reason
no one has bothered to improve it is that there is next to no use
for it anymore.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-07-07 19:03:06 Re: script binaries renaming
Previous Message Zdenek Kotala 2007-07-07 17:26:55 Re: script binaries renaming

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-07-07 19:03:06 Re: script binaries renaming
Previous Message Tom Lane 2007-07-07 18:31:03 Re: dblink connection security