4 ms·
The problem you can run into, and this will depend on the state of your optimizer, is that you may have a join, and the presence of the index may give you a nes
by cafard 14y ago
The problem you can run into, and this will depend on the state of your optimizer, is that you may have a join, and the presence of the index may give you a nested-loops path when a hash join would be more efficient.
- jeltz 14y agoThe PostgreSQL optimizer is cost based and uses statistics to choose join method. So that problem is quite rare and is best debugged using EXPLAIN/EXPLAIN ANALYZE.