<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The good and the bad about bind variables, revisited in 11g !</title>
	<atom:link href="http://www.pythian.com/news/543/the-good-and-the-bad-about-bind-variables-revisited/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/543/the-good-and-the-bad-about-bind-variables-revisited/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Sat, 20 Mar 2010 10:37:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: LSC</title>
		<link>http://www.pythian.com/news/543/the-good-and-the-bad-about-bind-variables-revisited/#comment-101286</link>
		<dc:creator>LSC</dc:creator>
		<pubDate>Mon, 17 Sep 2007 22:17:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/543/the-good-and-the-bad-about-bind-variables-revisited#comment-101286</guid>
		<description>Hi

The new adaptive cursor sharing seems good idea. I have done some tests and it seems that it stops peeking when it reaches a stability. For example if we have a table with 9 values with low cardinality and 1 with high if we start testing from low to high, since 1 to 9 has low cardinality the plan does not change (uses nice index range scan), when we reach to 10 we would expect a FTS but it does not seems to peek anymore and stays with index range scan plan. So not perfect yet...</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>The new adaptive cursor sharing seems good idea. I have done some tests and it seems that it stops peeking when it reaches a stability. For example if we have a table with 9 values with low cardinality and 1 with high if we start testing from low to high, since 1 to 9 has low cardinality the plan does not change (uses nice index range scan), when we reach to 10 we would expect a FTS but it does not seems to peek anymore and stays with index range scan plan. So not perfect yet&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
