Search Postgresql Archives

Bad estimates on GIN bigint[] index

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le 03/09/2019 à 15:43, Tom Lane a écrit :
"Arnaud L." <arnaud.listes@xxxxxxxxx> writes:
-> Bitmap Index Scan on planet_osm_ways_nodes_idx (cost=0.00..11190.36 rows=1420982 width=0) (actual time=0.268..0.268 rows=1 loops=1)
         Index Cond: (nodes && '{1}'::bigint[])

The planner should be able to do better than that, given up-to-date
statistics on the "nodes" column.


Sorry to up this thread, but is there anything I can do to help the planner in this particular case ? REINDEXing did not help, nor did ANALYZEing with different STATISTICS target for this specific column.


Regards
--
Arnaud





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux