<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt
0pt0pt 0.8ex; padding-left: 1ex;"> Secondly there's the whole retail vacuum problem -- any<br /> index entries
referringto this page would be left dangling unless<br /> there's some kind of retail vacuum or perhaps a page version
number.<br/><br /></blockquote></div><br />The issue, we can divide into two<br />a)volatile functions <br />b)broken
datatypes<br/><br />For a) I think volatile function issue can be resolved by using hidden columns in the heap itself.
Thiswill create a duplication of data, but since the index will get created on it, it will always point to the right
heaptuple<br /><br />For b) We are already suffering with this issue in any index lookups, index based updates/deletes,
uniqueconstraints, referential integrity maintenance etc. So hopefully one day we can extend this list to include more
:))<br/><br />Gokul.<br /><br />