Re: Command tags in create/drop scripts - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Command tags in create/drop scripts
Date
Msg-id 4660D3FF.2040503@dunslane.net
Whole thread Raw
In response to Re: Command tags in create/drop scripts  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: Command tags in create/drop scripts  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Zdenek Kotala wrote:
> Tom Lane wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> Zdenek Kotala wrote:
>>>> And what about replace all "scripts" by one command e.g pg_cmd with 
>>>> following interface:
>>>>
>>>> pg_cmd create database <...>
>>
>>> And we'll break a million applications that rely on the command names. 
>
> Compatibility is possible solve with parsing arg[0]. If old name 
> appears there command line will be parsed in old style... This 
> functionally should keep there for some transition interval. Packager 
> will be responsible if he create links for backward compatibility or not.

Well, I don't think rolling up the miscellaneous commands into a single 
binary with behaviour dependent on arg[0] is a bad idea. I don't think 
it's something to be looked at during feature freeze, though, especially 
given our backlog. I think we'd need a good long lead time before we 
removed the old names from our default install - at least one release 
cycle, so it would be two years or more before this became any sort of 
reality.

cheers

andrew




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: syslogger line-end processing infelicity
Next
From: Joe Conway
Date:
Subject: pg_detoast_datum_packed and friends