Re: Functions used in index definitions shouldn't be changed - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Functions used in index definitions shouldn't be changed
Date
Msg-id 546E42B1.3010108@dunslane.net
Whole thread Raw
In response to Re: Functions used in index definitions shouldn't be changed  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 11/20/2014 02:28 PM, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Thu, Nov 20, 2014 at 1:56 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
>>> I don't think that there is a universally compelling right or wrong to
>>> questions like this, it is more a matter of taste.  Is it more important to protect
>>> the casual DBA from hurting himself or herself, or is it more important to
>>> provide a well honed scalpel for the experienced surgeon?
>> +1.
>> I think if we had an already-existing prohibition here and you
>> proposed relaxing it, the howls would be equally loud.  We're not
>> entirely consistent about how picky we are.
> How's that quote about foolish consistency go?  In many cases, the reason
> why we enforce some things and not others is practical utility.


Right.

(FTR, the quote from Emerson goes "A foolish consistency is the 
hobgoblin of little minds, adored by little statesmen and philosophers 
and divines.")


cheers

andrew



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Functions used in index definitions shouldn't be changed
Next
From: Peter Geoghegan
Date:
Subject: Re: Doing better at HINTing an appropriate column within errorMissingColumn()