s. In general we saw fair amount of performance
improvement, but one thing that surprises us is that after around 20% tuples
updated we found oracle taking more time.
Regards,
Shrish Purohit |Senior Software Engineer|Persistent Systems
shrish_puro...@persistent.co.in |Cell:+91-9850-959-940|Tel:+91(20)302-3
Hi All,
continued from discussion mail
http://archives.postgresql.org/pgsql-hackers/2009-06/msg00971.php
>
>
>> - Am I reading the patch correctly that you do not end up creating
>> indexes on the children tables? That is a big problem!
>
>
>
So what expected is when an index is created on Parti
HI All,
I had gone through advantages of visibilitymap along with discussion on
thick index. I have a question.
when we have information about visibility of the data, does it make sense to
propagate values of expression stored in index through various slots of
execution tree?
It would be helpful w
HI All,
I had gone through advantages of visibilitymap along with discussion on
thick index. I have a question.
when we have information about visibility of the data, does it make sense to
propagate values of expression stored in index through various slots of
execution tree?
It would be helpful w
s we count same static slot, while for minmax_scan first
non-null tuple as the tuple with minium/maximum value.
Thanks,
Shrish Purohit | Software Engineer | Persistent Systems
shrish_puro...@persistent.co.in | Cell: +91 98509 59940 | Tel: +91 (20)
3023 4493
Innovation in software product design,
