the gin index but now it does
827k buffer reads to find 1 row. Why does it still want to use this gin index
vs using the other index I note above and why is it doing even more work when
removing the leading %?
3. If I disable bitmap scan it then prefers to full scan the ta
Both of the below visualizers can help, but require some knowledge about
comparing estimated vs actual row estimates, disk sorts vs in memory,
etc. Drawing implications about whether your schema needs to change or just
the query will take time to master as well.
http://tatiyants.com/pev/#/plans/ne
Hello.
At Tue, 1 Oct 2019 12:42:24 +0530, Sonam Sharma wrote in
> We have a query which is running slow and it's taking 26secs to complete..
> we have run the analyzer also and it's taking the same time.
>
> Any tool is there for query optimization or any suggestions.
EXPLAIN ANALYZE (not jus
We have a query which is running slow and it's taking 26secs to complete..
we have run the analyzer also and it's taking the same time.
Any tool is there for query optimization or any suggestions.
My query plan looks like this :
CTE Scan on approvalwflscreen (cost=8736.21..8737.25 rows=52 width=
