Simon Riggs wrote:
> > What if we only applied
> > HOT to primary-key indexes, so that there was certainly not more than
> > one index per table that the property applies to?
>
> On its own, I don't think this is a sufficiently wide use-case.
>
> Perhaps we should do this PLUS make HOT-semantics optional for each
> additional index. i.e. HOT is always enforced on primary indexes and
> optionally on other indexes (but not by default).
Here's is a very simple, low-tech idea. How about checking whether the
new index requires chilling tuples; if it does, then elog(ERROR) until
all the indexes have been manually chilled, which would be done with an
"ALTER INDEX ... CHILL" command or something like that. Only when all
indexes are known chilled, you can create another one, and then the user
can "hotify" indexes as appropriate.
(Disclaimer: I haven't followed the HOT design closely to know if this
makes enough sense)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
