Re: Minmax indexes - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Minmax indexes
Date
Msg-id CAGTBQpZuB3i8Pk2fzVSFjuogjvwPugr_V-hOXvA5TM_rcxWLhw@mail.gmail.com
Whole thread Raw
In response to Re: Minmax indexes  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
On Fri, Jul 11, 2014 at 3:47 PM, Greg Stark <stark@mit.edu> wrote:
> On Fri, Jul 11, 2014 at 6:00 PM, Claudio Freire <klaussfreire@gmail.com> wrote:
>> Marking as read-only is ok, or emitting a NOTICE so that if anyone
>> changes those parameters that change the shape of the index, they know
>> it needs a rebuild would be OK too. Both mechanisms work for me.
>
> We don't actually have any of these mechanisms. They wouldn't be bad
> things to have but I don't think we should gate adding new types of
> indexes on adding them. In particular, the index could just hard code
> a value for these parameters and having them be parameterized is
> clearly better even if that doesn't produce all the warnings or
> rebuild things automatically or whatever.


No, I agree, it's just a nice to have.

But at least the docs should mention it.



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Minmax indexes
Next
From: Tom Lane
Date:
Subject: Over-optimization in ExecEvalWholeRowVar