I thought also in the past about a query-optimization tracking project, which could be used in addition or instead (e.g., as a column- it would be broader than this), to group all WMF query performance issues in production.

Maybe #mariadb-query-optimization to cover both? Would this be mysql/mariadb specific, or also cover postgres etc issues/topics?

In T233589#5515440, @Aklapper wrote:

Maybe #mariadb-query-optimization to cover both? Would this be mysql/mariadb specific, or also cover postgres etc issues/topics?

This will be only for mariadb yes.
I am not sure if I want to get both under the same tag, I thought just a tag for cases where the optimizer behaves unexpectedly. For me, query optimization also involves queries that are not well formed, and in this case, the queries are as good as they can be and it is just the optimizer choosing the wrong plan just because.
That's why I wanted just the optimizer-bug on the tag.

We can of course create another project with query-optimization that can cover mariadb, postgres and more DBs in general.

Any ETA on when this tag could be created?
Thanks!

@Marostegui If it takes too much time, and the general one has been created you can use that + Upstream meanwhile.

In T233589#5546100, @Marostegui wrote:

Any ETA on when this tag could be created?

Whenever I get the impression feeling that there is some consensus among the people who plan to use the tag. :) I guess I misinterpreted "I am not sure if I want to get both under the same tag" as "I am not sure" instead of "No" so I can go ahead with #mariadb-optimizer-bug. Any tag description?

I think we can go for: "MariaDB optimizer unexpected behaviours" or something like that.
The idea is to be able to group those tasks where we've detected the optimizer behaving unexpectedly and choosing a query plan that is worse than it should be.

Thanks!