Skip to content

Conversation

@asfernandes
Copy link
Member

No description provided.

@asfernandes asfernandes self-assigned this Jul 23, 2025
@dyemanov
Copy link
Member

dyemanov commented Jul 23, 2025

I suggest to defer this PR until we resolve the known performance regressions in the existing code. Otherwise, new indices may hide these issues (allowing better plans than now), but strike back later when the new "backward compatibility" indices are removed.

@asfernandes
Copy link
Member Author

Do we still have these performance problems?

@dyemanov
Copy link
Member

Do we still have these performance problems?

AFAIK no, but I will double-check the old cases and report back.

@dyemanov
Copy link
Member

dyemanov commented Oct 7, 2025

I've double-checked all regression cases reported by Pavel after schemas were merged and found that all of them are currently fixed. We seem to still have performance issues, as reported here, but I don't think they're related to system query plans and should be researched separately.

@asfernandes asfernandes merged commit 3e3b75f into master Oct 7, 2025
46 checks passed
@asfernandes asfernandes deleted the work/no-schema-indexes branch October 7, 2025 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants