8000 Feedback: Database Schemas - perhaps incorrect/unhelpful guidance on large number of schemas · Issue #19624 · cockroachdb/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feedback: Database Schemas - perhaps incorrect/unhelpful guidance on large number of schemas 92B4 #19624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hand-crdb opened this issue May 21, 2025 · 0 comments

Comments

@hand-crdb
Copy link
hand-crdb commented May 21, 2025

Page: https://cockroachlabs.com/docs/v25.2/schema-design-overview.html

What is the reason for your feedback?

[ ] Missing the information I need

[ ] Too complicated

[ ] Out of date

[ ] Something is broken

[X] Other

Additional details

The page says

The number of databases or schemas on the cluster has minimal impact on the total number of tables that it can support.

This implies that a CockroachDB cluster can support a large number of schemas, which is not the case. Please consult with the engineering team to reword this in a way that more accurately reflects the impact of large numbers of non-table objects, including schemas. Anecdotally, I have heard that CockroachDB has problems with a large total number of object descriptors, rather than the numbers of specific types of database objects.

Note that different subsystems may be impacted differently. So, for example, query performance may be acceptable but other database components, such as the DB Console or backups, may fail or perform poorly.

As a specific example for schemas, performed a simple test. I created 20000 schemas on a CockroachDB cluster. SQL queries against tables in these schemas seemed to perform fine, but a SHOW SCHEMAS query took an extremely long time to run.

THANK YOU

Jira issue: DOC-13736

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

No branches or pull requests

1 participant
0