<br /><br /><div class="gmail_quote">On Thu, Feb 25, 2010 at 3:16 AM, Gokulakannan Somasundaram <span dir="ltr"><<a
href="mailto:gokul007@gmail.com">gokul007@gmail.com</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br
/><divclass="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt
0pt0pt 0.8ex; padding-left: 1ex;">I haven't thought about whether this is sufficient but if it is then<br /> an initial
usefulthing to add would be to use it for queries where we<br /> have a qual that can be checked using the index key
eventhough we<br /> can't do a range scan. For example if you have a btree index on<br /> <a,b,c> and you have a
WHEREclause like "WHERE c=0"<br /><br /> That would be a much smaller change than IOT but it would still be a<br />
prettybig project. Usually the hardest part is actually putting the<br /> logic in the planner to determine whether
it'sadvantageous. I would<br /> suggest waiting until after 9.0 is out the door to make sure you have<br /> the
attentionof Heikki or Tom or someone else who can spend the time<br /> to check that it will actually work before
puttinglots of work coding<br /> it.<br /><br /></blockquote></div></div>I will try that. Thanks ...<br
/></blockquote></div><br/>Some more ideas popped up. I am just recording those.<br />a) In place of block id( this has
tobe issued for every new/recycled block and it is not there in postgres), we can even have SnapshotNow's transaction
id.I just feel the synchronization effect will be more here.<br /> b) We can just record the currentTimestamp in the
page.While this is without any synch, it might create problems, when we decide to go for Master-Master replication and
Distributeddatabases. So when such things happens, the clock on the various systems have to be synched.<br /><br
/>Gokul.<br/>
