On Fri, 2007-03-16 at 16:59 -0400, Alvaro Herrera wrote: > 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.
Well, I've spent two weeks searching for a design that does CREATE INDEX without changing existing functionality. What's been proposed is very close, but not exact. CREATE INDEX CONCURRENTLY can work, so we're just discussing the other increasingly edgy cases. I agree some kind of compromise on CREATE INDEX seems to be required if we want HOT without some drastic reductions in function. I'm happy to go for low tech approaches, or anything really. Simple is good, so we can hit feature freeze. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
