Henrik Zagerholm <henke@mac.se> writes:
> Usually I can see what is wrong with queries but I can't figure out
> why this query is slow.
Seems the main problem is here:
> -> Bitmap Index Scan on tbl_archive_idx1
> (cost=0.00..1150.47 rows=8 width=0) (actual time=1505.456..1505.456
> rows=86053 loops=16)
> Index Cond: (tbl_share.pk_share_id =
> tbl_archive.fk_share_id)
Why is this scan finding so many more rows than the planner expects?
Perhaps increasing the stats targets on these columns would help it
make a better estimate.
regards, tom lane