> > >> Does it scan log_destination for slow (as > defined by log_min_duration_statement) queries, or maybe keep a history of > slow queries? > > Because *that* is what determines what indices are needed. > > -- > Death to <Redacted>, and butter sauce. > Don't boil me, I'm still alive. > <Redacted> lobster! > Thank you for the suggestion.
The current version of Pg_dbscanner does not analyze log_destination or maintain a history of slow queries. The current recommendations are based on the table schema, column data types, existing indexes, and PostgreSQL catalog information using a heuristic-based approach. I agree that actual query workload and slow queries are important factors when determining whether an index would be useful. This is not currently part of the extension, but it would be a useful enhancement to make the recommendations more workload-aware. Thank you for pointing this out. I’ll consider this for future development of the extension. Regards, Lakshmi
