Re: Command tags in create/drop scripts

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Command tags in create/drop scripts
Date: 2007-06-09 14:12:09
Message-ID: 15904.1181398329@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Jim C. Nasby wrote:
>> On Tue, Jun 05, 2007 at 05:52:39PM -0000, Andrew Hammond wrote:
>>> +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

> +1

I like this better than the original proposal, too. Doing more than
this seems like more work and more confusion for users than the problem
justifies.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-06-09 14:22:04 Re: Issues with factorial operator
Previous Message Tom Lane 2007-06-09 14:01:51 Re: Binary mode copy in from stdin