Post

The idea was to start with only the access paths that consume the most response time or resources and then see how frequently the queries are actually executed *and* show cardinality estimates/filter factors ("needle in the haystack?") and propose *better* indexes (not more).

But it became clear that more than just a single SQL query is needed, for example you wouldn't see a filter predicate on a table if CBO ended up doing a full scan and just throwing rows away much higher up in some hash join. I was going to write a Python tool or something...

... but now it looks like I'll just feed the relevant info into a language model instead. Let's see how it goes! Nevertheless, people have found this tool already useful in the past! backendtales.blogspot.com/2023/02/sant...