Hi,
I was wondering if we can apply the same logic of recalculating OldestXmin within IndexBuildHeapScan which occurs as part of create index operation?
Having to index lesser number of tuples should be a good save in the "CREATE INDEX CONCURRENTLY" case, if the above is possible?
Regards,
Nikhils
--
EnterpriseDB
http://www.enterprisedb.com