Question: How can you check the status of a PostgreSQL cluster?


Checking the status of a PostgreSQL cluster is crucial for database administration, ensuring that all components of the cluster are functioning correctly and efficiently. Here’s how you can perform this check:

1. Using the pg_lsclusters Command

If you’re using PostgreSQL on a Debian-based system, the pg_wrapper utilities include the pg_lsclusters command, which lists all PostgreSQL clusters. This command provides a quick overview of the status, version, and other key details of each cluster.


You will get output like:

Ver Cluster Port Status Owner    Data directory               Log file
12  main    5432 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log

2. Checking PostgreSQL Service Status

You can check if the PostgreSQL service is active which indirectly tells you about the cluster status. This can be done using:

sudo systemctl status postgresql

This command checks the status of the PostgreSQL service, which should be active (running) if the cluster is up.

3. Using SQL Queries to Check Cluster Health

Connect to your PostgreSQL database and run SQL queries to ensure the database is responding to commands.

SELECT version();

This query returns the version of PostgreSQL running, confirming that the database cluster can execute queries.

4. Reviewing the PostgreSQL Logs

PostgreSQL logs provide a wealth of information including error messages and warnings that can indicate problems with a PostgreSQL cluster.

The location of the log files depends on your PostgreSQL configuration but often found in /var/log/postgresql/.

To review the latest entries in the log file, you might use:

tail -f /var/log/postgresql/postgresql-12-main.log

5. Checking Connectivity

Ensure that all nodes within the cluster can communicate with each other. This is particularly critical in setups like streaming replication or when using extensions like Pgpool-II or Postgres-XL.

psql -h node_hostname -U username -d databasename -c 'SELECT 1;'

Replace node_hostname, username, and databasename with actual values relevant to your cluster setup.

By regularly checking these aspects, you can ensure your PostgreSQL cluster remains healthy and operational.

Was this content helpful?

White Paper

Free System Design on AWS E-Book

Download this early release of O'Reilly's latest cloud infrastructure e-book: System Design on AWS.

Free System Design on AWS E-Book
Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.