Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Functions used in index definitions shouldn't be changed
Date
Msg-id CA+TgmoaGXzNeh08SOR13A3=sNyR135rREPmxXB-wStcjnCi6hQ@mail.gmail.com
Whole thread Raw
In response to Re: Functions used in index definitions shouldn't be changed  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Responses Re: Functions used in index definitions shouldn't be changed  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Functions used in index definitions shouldn't be changed  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-hackers
Tree view 
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Doing better at HINTing an appropriate column within errorMissingColumn()
Next
From: Tom Lane
Date:
Subject: Ripping out dead code for mark/restore in some plan types