@@ -1382,8 +1382,8 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
13821382 </para>
13831383
13841384 <para>
1385- Indexes can be usedvia either simple index scans or <quote>bitmap</>
1386- index scans . In a bitmap scan
1385+ Indexes can be usedby simple index scans, <quote>bitmap</> index scans,
1386+ and the optimizer . In a bitmap scan
13871387 the output of several indexes can be combined via AND or OR rules,
13881388 so it is difficult to associate individual heap row fetches
13891389 with specific indexes when a bitmap scan is used. Therefore, a bitmap
@@ -1393,6 +1393,9 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
13931393 <structname>pg_stat_all_tables</>.<structfield>idx_tup_fetch</>
13941394 count for the table, but it does not affect
13951395 <structname>pg_stat_all_indexes</>.<structfield>idx_tup_fetch</>.
1396+ The optimizer also accesses indexes to check for supplied constants
1397+ whose values are outside the recorded range of the optimizer statistics
1398+ because the optimizer statistics might be stale.
13961399 </para>
13971400
13981401 <note>