<br />HI All, <br /><br />I had gone through advantages of visibilitymap along with discussion on thick index. I have a
question.<br />when we have information about visibility of the data, does it make sense to propagate values of
expressionstored in index through various slots of execution tree?<br /> It would be helpful when index is created on
immutablefunction or expression. <br /><br />I am adding additional columns in the heap tuple returned by index with
theexpression values stored in the index. For index_only_scan while projecting the values we will treat expression as
normalcolumn. It is simple for queries with single table. But, when we have joins, we will need to modify plan to treat
expressionas normal column. This will involve modifying plan, intermediate slots. Modification in the plan need to be
performed after finalizing plan, as we will be able to identify whether we can treat the expression as value only then.
<br/><br />Can there be any other alternative? <br /><br />Thanks, <br />Shrish<br /><br /><br />
