On 05/29/21 07:08, Dean Gibson (DB Administrator) wrote: [deleted]
BTW what is the planner reason to not use index in v13.2? Is index in corrupted state? Have you try to reindex index "FccLookup"."_LicStatus_pkey" ?
1.5M of seqscan's are looking really bad.
SubPlan 2
-> Limit (cost=0.15..8.17 rows=1 width=32) (actual time=0.006..0.007 rows=1 loops=55)
-> Index Scan using "_LicStatus_pkey" on "_LicStatus" (cost=0.15..8.17 rows=1 width=32) (actual time=0.005..0.005 rows=1 loops=55)
Index Cond: ("_HD".license_status = status_id)
SubPlan 2
-> Limit (cost=0.00..1.07 rows=1 width=13) (actual time=0.001..0.001 rows=1 loops=1487153)
-> Seq Scan on "_LicStatus" (cost=0.00..1.07 rows=1 width=13) (actual time=0.000..0.000 rows=1 loops=1487153)
Filter: ("_HD".license_status = status_id)
Rows Removed by Filter: 1
Doing your REINDEX didn't help. Now in the process of reindexing the entire database. When that's done, I'll let you know if there is any improvement.
