How to Check Database Size in PostgreSQL: Your Quick Guide

By Cristian G. Guasch • Updated: 09/22/23 • 9 min read

Stepping into the world of databases, I’ve often found myself needing to determine the size of a PostgreSQL database. Whether it’s for capacity planning, monitoring growth over time, or just out of sheer curiosity, knowing how to check database size in PostgreSQL can be incredibly handy.

A question that I commonly hear is – “How do you check the size of a PostgreSQL database?” Well, my friends, it’s not as complicated as you might think. The process involves some simple SQL queries that anyone with basic knowledge of SQL can execute. These queries retrieve information from PostgreSQL system catalogs and provide us with precise measurements related to our data.

By the end of this guide, you’ll have a clear understanding on how to measure your own PostgreSQL database sizes. So let’s dive right in and start exploring these valuable commands together!

Understanding PostgreSQL Database Size

When I’m dealing with PostgreSQL, one of the first things I’ve learned to check is the size of my database. It’s not just about managing storage space; understanding your database size can give you insights into performance and help you plan for future growth.

In PostgreSQL, there are two major components that make up the total size: the base data and indexes. The base data includes all your tables and their corresponding rows, while indexes are special lookup structures associated with your tables to speed up data retrieval.

Here’s a basic example of how you might check your total database size in PostgreSQL:

SELECT pg_size_pretty(pg_database_size('your_database_name'));

This command will return the size of ‘your_database_name’ in a human-readable format. You’ll need to replace ‘your_database_name’ with the name of your actual database.

But what if you want more granular details? What if you’d like to know how much space each table or index takes up? That’s where this script comes in handy:

   relname AS "Table",
   pg_size_pretty(pg_total_relation_size(relid)) As "Size"
   pg_total_relation_size(relid) DESC;

Executing this SQL statement will provide a list of all user tables ordered by their sizes, including both base data and indexes.

However, be careful when interpreting these results! It’s common for beginners to think that reducing table sizes will immediately free up disk space. In reality, PostgreSQL uses something called MVCC (Multi-Version Concurrency Control) which can cause disk space usage to fluctuate over time due to transactional processing. This means that even after deleting data from a table, disk space may not be freed immediately.

So remember – keeping tabs on your PostgreSQL database size isn’t only about managing storage. It’s also about understanding your data, planning for growth and ensuring optimal performance. Remember to periodically check the size of your database, its tables and indexes – this habit will go a long way in helping you maintain a healthy, efficient database!

Prerequisites for Checking Database Size in PostgreSQL

Before we dive into how to check database size in PostgreSQL, let’s first ensure that we’ve got a few essentials covered. It’s important to have some pre-requisites in place to make the process smoother and more efficient.

First off, you’ll need access to a running PostgreSQL database. This might seem obvious, but it’s necessary nonetheless. Whether it’s on your local system or hosted remotely, make sure it’s up and running.

Secondly, you should have the required permissions to execute SQL statements on the database. Quite often, this will require having ‘superuser’ or ‘database owner’ privileges. Otherwise, you won’t be able to run the commands needed to get the information about the database size.

-- You can use this command to verify your current user role
SELECT current_user;

Next up is understanding some basic SQL (Structured Query Language) syntax and commands. We’re going to be using SQL queries directly on our PostgreSQL server using an interface like psql (PostgreSQL’s interactive terminal), PGAdmin4 or another preferred tool.

Lastly, having a good grasp of units of measurement will also come in handy when interpreting the results. PostgreSQL typically reports database sizes in bytes – which can quickly become large numbers that are hard for humans to interpret! Understanding how bytes translate into kilobytes (KB), megabytes (MB), gigabytes (GB), and so forth will help make sense of these numbers.

Here are some common conversions:

  • 1 Kilobyte = 1024 Bytes
  • 1 Megabyte = 1024 Kilobytes
  • 1 Gigabyte = 1024 Megabytes

In summary: before checking database sizes in PostgreSQL make sure you have appropriate access rights; familiarity with SQL syntax and commands; an active connection with a running PostgreSQL instance; plus an understanding of data storage units. We’re now all set to dive into the specific commands for checking database sizes in PostgreSQL. So let’s dive right into the nitty-gritty of checking your PostgreSQL database size. You’ll need to make use of SQL queries for this task, and I’m here to guide you through each step.

First off, open up your PostgreSQL command line tool (psql), which gives direct access to your databases. From there, log in with the necessary credentials. Now you’re all set to start querying!

To get an overview of total disk space used by all databases, you’ll want to use this simple query:

SELECT pg_size_pretty(pg_database_size(pg_database.datname)) AS size_in_mb,
pg_database.datname as database_name 
FROM pg_database ORDER BY pg_database_size(pg_database.datname) DESC;

Run this command and voila! It will return a list of all databases along with their sizes in a pretty format.

But what if you want information on just one specific database? Don’t worry – we’ve got that covered too! Substitute ‘your_database’ in the following query with the name of your own database:

SELECT pg_size_pretty(pg_database_size('your_database'));

This will give you the size of that particular database.

Now don’t forget: both these commands only provide data sizes without indexes. If you’d like to include those, add pg_total_relation_size instead of pg_database_size. It’s important not to mix these up!

Common mistakes when running these queries are typos or incorrect syntax. SQL is unforgiving if a single character or space is out of place! So always double-check before hitting enter. Remember also that case matters: ‘Your_Database’ and ‘your_database’ are considered two entirely different entities.

Hope this helps streamline your PostgreSQL management tasks! Just remember – it’s all about precision and attention to detail when working with databases.

Common Issues and Solutions When Checking PostgreSQL Database Size

Diving deep into the world of PostgreSQL, it’s not uncommon to run into a few hurdles along the way. For instance, when you’re trying to check database size in PostgreSQL, you might encounter some common issues. But don’t fret! I’m here to guide you through these challenges with simple solutions.

One typical problem could be insufficient privileges. You see, only superusers, or users with appropriate permissions can check the size of databases. So if you’re getting an error message saying “permission denied”, then this is probably why. It’s easy enough to solve though! Here’s how:

GRANT pg_read_all_stats TO username;

Just replace username with your actual username and voila!

Another issue that sometimes trips folks up is forgetting that table and schema names are case sensitive in SQL queries. If you’re typing in lower-case letters but the actual name contains upper-case letters (or vice versa) then the query won’t return accurate results. The solution? Always use double quotes around names:

SELECT pg_size_pretty(pg_database_size("YourDatabase"));

A third common mistake is neglecting to refresh materialized views before checking their sizes. This can result in outdated information being displayed as materialized views don’t update automatically when data changes are made to underlying tables.

Here’s what refreshing a materialized view looks like in SQL:


Lastly, make sure your version of PostgreSQL supports the functions you’re using for checking database size: pg_size_prettypg_total_relation_size, etc., were all added at different versions of PostgreSQL – so always double-check!

And there we have it! These are some of the most common issues when trying to determine database sizes in PostgreSQL along with their solutions. With these tips up your sleeve, you’re well on your way to mastering PostgreSQL database management.

Conclusion: Maximizing Efficiency with Database Size Knowledge

Understanding how to check the size of your PostgreSQL database isn’t just a neat trick, it’s an essential knowledge that can help maximize efficiency in numerous ways. For starters, knowing the exact size of your database gives you a clear picture of the storage space you’re currently utilizing. This can be vital when planning for scalability and growth.

Take for instance this simple command:

SELECT pg_size_pretty(pg_database_size('your_database_name'));

Replace ‘your_database_name’ with the name of your database and voila! You’ve got the size. It’s as easy as whipping up a cup of coffee!

However, don’t let its simplicity fool you. I’ve seen numerous developers make common mistakes like forgetting to replace ‘your_database_name’ or incorrectly typing their own database’s name. These errors might seem minor but they can lead to incorrect results or even worse – no results at all!

Another crucial factor is that having this information at hand helps in optimizing data retrieval times. When you’re aware of your database size, you’re better equipped to design efficient queries and manage indexes more effectively.

Let’s consider:

SELECT *,pg_size_pretty(total_bytes) AS total 
    , pg_size_pretty(index_bytes) AS INDEX 
    , pg_size_pretty(toast_bytes) AS toast 
    , pg_size_pretty(table_bytes) AS TABLE  
  FROM (
  SELECT *, total_bytes-index_bytes-COALESCE(toast_bytes,0) AS table_bytes 
    FROM (
      SELECT c.oid,nspname AS table_schema, relname AS TABLE_NAME 
          , c.reltuples AS row_estimate
          , pg_total_relation_size(c.oid) AS total_bytes
          , pg_indexes_size(c.oid) AS index_bytes
          , COALESCE(pg_total_relation_size(reltoastrelid), 0) AS toast_bytes
      FROM pg_class c
      LEFT JOIN pg_namespace n ON n.oid = c.relnamespace
      WHERE relkind = 'r'
  ) a) a;

This command gives you the total size, index size, toast size, and table size. With this information, you can make more informed decisions about index management and data retrieval strategies.

In conclusion, while checking your PostgreSQL database size might seem like a trivial task on the surface, it’s actually an essential tool in maximizing efficiency. So next time you’re working with PostgreSQL databases, make sure to have these commands at your fingertips!

Related articles