Posted over 2 years ago. Visible to the public.

Checking database size by row count

As an application exists, data accumulates. While you'll be loosely monitoring the main models' record count, some supportive database tables may grow unnoticed.

To get a quick overview of database table sizes, you can view the row count like this:


SELECT schemaname,relname,n_live_tup FROM pg_stat_user_tables ORDER BY n_live_tup DESC LIMIT 12; schemaname | relname | n_live_tup ------------+------------------------------------------------+------------ public | images | 17025 public | items | 16918 public | tree_nodes | 5018 public | page_versions | 4049 public | pages | 3919

Please note that this does not work reliably on database slaves Archive .


SELECT table_name, table_rows FROM information_schema.tables WHERE table_schema = (SELECT database()) ORDER BY table_rows DESC LIMIT 12; +---------------------+------------+ | table_name | table_rows | +---------------------+------------+ | addresses | 48106 | | orders | 33740 | | users | 8703 | | ...

If you're interested in the space a table takes up on the disk check table sizes by disk usage instead.

Flaky tests are tests that sometimes fail for no obvious reason. They are the plague of many end-to-end (E2E) test suites that automate the browser through tools like Capybara and Selenium.

Join our free training event and learn to fix any flaky test suite, even in large legacy applications.

Owner of this card:

Dominik Schöler
Last edit:
9 months ago
by Michael Leimstädtner
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Dominik Schöler to makandra dev
This website uses short-lived cookies to improve usability.
Accept or learn more