On Mon, Mar 19, 2007 at 12:05:19PM +0000, Simon Riggs wrote: > I was unwilling to compromise to have HOT if only one index existed, but > IMHO allowing HOT with <= 3 indexes is an acceptable compromise for this > release. (We can always use vertical partitioning techniques to allow > additional access paths to be added to the same table - I'd be very > happy to document that with worked examples, if requried).
I'm not sure where we're sitting with this, but I've got another idea I haven't seen (one that I think is better than an arbitrary limit on the number of indexes)... what if we just disallow non-concurrent index builds on hot tables? It sounds like the additional pain involved in chilling an entire table and keeping it chilled for the index build is even more overhead than just doing a concurrent index build. -- Jim Nasby [EMAIL PROTECTED] EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
