官术网_书友最值得收藏!

Using bitmap scans effectively

The question naturally arising now is: when is a bitmap scan most beneficial and when is it chosen by the optimizer? From my point of view, there are really two use cases:

  • Avoiding using the same block over and over again
  • Combining relatively bad conditions

The first case it quite common. Suppose you are looking for everybody who speaks a certain language. For the sake of the example, we can assume that 10% of all people speak the required language. Scanning the index would mean that a block in the table has to be scanned all over again as many skilled speakers might be stored in the same block. By applying a bitmap scan, it is ensured that a specific block is only used once, which of course leads to better performance.

The second common use case is to use relatively weak criteria together. Let's suppose we are looking for everybody between 20 and 30 years of age owning a yellow shirt. Now, maybe 15% of all people are between 20 and 30 and maybe 15% of all people actually own a yellow shirt. Scanning a table sequentially is expensive, and so PostgreSQL might decide to choose two indexes because the final result might consist of just 1% of the data. Scanning both indexes might be cheaper than reading all of the data.

主站蜘蛛池模板: 广宁县| 普格县| 天等县| 麻江县| 金溪县| 朝阳县| 宁南县| 玛纳斯县| 隆安县| 武鸣县| 罗甸县| 剑阁县| 江门市| 晋州市| 裕民县| 靖远县| 木里| 历史| 岐山县| 高阳县| 滦平县| 皮山县| 偃师市| 集安市| 凉山| 会昌县| 徐闻县| 威宁| 富锦市| 洛浦县| 明光市| 西吉县| 赤城县| 光泽县| 通城县| 浏阳市| 安西县| 广元市| 漠河县| 绥滨县| 宁海县|