>> Either state of indcheckxmin is valid with all three of these >> combinations, so the specific kluge I was contemplating above doesn't >> work. But there is no valid reason for an index to be in this state: >> indisvalid = true, indisready = false
> Yeah, this looks much better, given our inability to add a new catalog > column in 9.2. Can we cheat a little though and use a value other than 0 > and 1 for indisvalid or indisready to tell the server to interpret it > differently ?
No, not unless you'd like "select * from pg_index" to misbehave. Personally, I like being able to look at catalogs.
Hmm.. I thought so. Thanks.
If we add a new column to the catalog for HEAD, I think it will be a good idea to add an "indflags" kind of column which can store a bitmap of flags. We probably don't get into this kind of situation often, but if we do, then we can more flexibility without impacting rebuilding the catalogs. My two cents.
