Description

Currently

On the browse rows page, console makes two concurrent queries:

1. A query to fetch the first 10 rows and make an estimated count
2. A query to get exact count

This query to get exact count overloads the database if the the table has large amount of data.

Fix

The browse rows page makes:

1. A query to fetch the first 10 rows and make an estimated count
2. If the estimated count is greater than 100000, the count is not shown (as the estimated count doesnt yet account for filters) and the pagination is rendered based on the estimated count.
3. If the estimated coutn is less than 100000, a query is made to fetch the exact count asynchronously. Until the exact count is fetched, the UI is rendered based on the estimated count.

Changelog

• CHANGELOG.md is updated with user-facing content relevant to this PR.

Affected components

• Server
• Console
• CLI
• Docs
• Community Content
• Build System
• Tests
• Other (list it)

Related Issues