The table search feature is great, but it only searches in the currently selected schema. This means navigating between and searching for tables is quite annoying when you have multiple schemas. A simple "search all schemas" toggle would save us lots of time.
Axel suggests a feature to enhance the table search functionality by allowing searches across all schemas, rather than just the currently selected one. This would improve navigation and usability for projects with multiple schemas, as developers often remember table names but not their specific schemas. Hardik K supports this idea, highlighting the benefits for large projects and suggesting additional enhancements like schema-aware results and keyboard shortcuts.
This would be a really useful quality-of-life improvement for projects with multiple schemas.
Right now, the table search being scoped only to the currently selected schema makes navigation noticeably slower once a project grows beyond a simple public schema setup. In larger applications, it’s common to organize tables across schemas for domains like:
authbillinganalyticsinternalstorageauditmulti-tenant partitionsIn those cases, developers often remember the table name but not necessarily which schema it belongs to. Having to manually switch schemas just to search introduces unnecessary friction in day-to-day workflows.
A global “search across all schemas” option would significantly improve discoverability and navigation speed, especially for teams managing large Postgres projects.
Some ideas that could make the feature even stronger:
billing.invoices, analytics.events, etc.)Even something lightweight like:
Search tables...
☑ Search across all schemas
would already solve most of the usability issue.
This also aligns well with how developers typically navigate IDEs/codebases — global search tends to scale much better than context-scoped search once projects become large.
Related references:
Definitely seems like a worthwhile UX improvement for the dashboard.