Secondly there's the whole retail vacuum problem -- any
index entries referring to this page would be left dangling unless
there's some kind of retail vacuum or perhaps a page version number.
The issue, we can divide into two
a)volatile functions
b)broken datatypes
For a) I think volatile function issue can be resolved by using hidden columns in the heap itself. This will create a duplication of data, but since the index will get created on it, it will always point to the right heap tuple
For b) We are already suffering with this issue in any index lookups, index based updates/deletes, unique constraints, referential integrity maintenance etc. So hopefully one day we can extend this list to include more :))
Gokul.
