/explore
|
You are here 
|
tanelpoder.com | ||
| | | | |
blog.tanelpoder.com
|
|
| | | | | Hello all fellow Oracle geeks and technology enthusiasts! Long time no see ;-) In the hacking session about Oracle full table scans and direct path reads I explained how the direct path read decision is not done by the optimizer, but instead during every execution, separately for every single segment (partition) scanned in the query. I also explained how the _small_table_thresholdparameter and theX$KCBOQH.NUM_BUF(which keeps track of how many buffers of any segment are currently cached) are used for determining whether to scan using direct path reads or not. - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. | |
| | | | |
optimizermagic.blogspot.com
|
|
| | | | | This blog post has moved here http://blogs.oracle.com/optimizer/entry/whats_changed_between_my_new_query_plan_and_the_old_one | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | | | I've discussed the capabilities of the dbms_xplan package in a couple of posts already; and shown how useful it can be in two examples: understanding a problem with filter subquery selectivity and understanding why some Cartesian merge joins were appearing unexpectedly. Let me make a crucial point about execution plans (again): if you have a... | |
| | | | |
kerryosborne.oracle-guy.com
|
|
| | | |||
