Re: @ versus ~, redux - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: @ versus ~, redux
Date
Msg-id 44FB1580.5040001@commandprompt.com
Whole thread Raw
In response to @ versus ~, redux  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: @ versus ~, redux  (Oleg Bartunov <oleg@sai.msu.su>)
List pgsql-hackers
> I can see various things that we might consider doing:
> 
> 1. Just flip the names of the two operators added by the GIN patch.
> 
> 2. #1 plus flip the names of the various contrib operators that are
>    out of sync (Michael Fuhr points out that contrib/intarray is out
>    of step too ... are there others?).
> 
> 3. Leave the existing op names as-is in core and contrib, but consider
>    them deprecated and add new ops with consistently-chosen names.
>    (The new ops introduced by GIN should only exist with the new names.)
> 
> #1 isn't doing anything towards solving the underlying problem.
> #2 has got obvious backwards-compatibility issues for contrib users.

+1 on #2 with the following caveat. When we publish the release notes, 
we have a specific section that says:

Compatibility changes from previous releases. Which IMHO should be there 
anyway as there are always compatibility issues from release to release.

Joshua D. Drake

-- 
   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240   Providing the most comprehensive  PostgreSQL
solutionssince 1997             http://www.commandprompt.com/
 




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: @ versus ~, redux
Next
From: Oleg Bartunov
Date:
Subject: Re: @ versus ~, redux