PostgreSQL backups can be categorized into two types: logical and physical. This post briefly covers each type and discusses the situations where you would use either one.
We'll cover some of the many tools you can use for Postgres backups in future posts.
This form of backup is typically achieved by translating all the data into a set of SQL commands and writing it into a single file. This can then be fed to any database cluster to recreate everything. In your CLI, performing logical backups can be as easy as:
pg_dump db_name > file_name.sql
for a single database, and:
pg_dumpall > file_name.sql
for an entire database cluster. Both the pg_dump and pg_dumpall utilities have their respective additional options for you to choose from and set up your desired logical backup setting. Recovering from them is comparably as simple:
psql -d db_name -f file_name.sql
What is it good for?
Simpler and quicker way of performing backups
As shown above, a single command is enough to perform a logical backup and another to recover from it. As a novice with databases, this would be an ideal and non-intimidating ensure that your database is backed up at all times.
Migration between different major versions of Postgres
If you are planning to migrate to a different major version of Postgres (for example, from Postgres 11 to Postgres 12), logical backups via
pg_dumpall would surely be your tool of choice. This is mainly because internal data storage formats may differ between major versions. This is the basis of physical backups, eliminating it as an option when upgrading. We'll go deeper into migrations and how to perform them in another post.
Backing up a single specific database
pg_dump, you can constantly back up a single, targeted database.
Physical backups pertain to the actual set of files or file systems where your database data is stored. One option for physical backups involves taking a snapshot of your data files by making a copy of them.
What is it good for?
More ideal for larger databases
As your database grows to the size of a few gigabytes, backing it up through physical backups is more ideal than through logical backups. As explained here, over time, performing logical backups in large databases could lead to degraded performance for other queries. Given the long run time as well to successfully perform a logical backup on a large database, errors have a higher chance of occurring, making the eventual backup unusable.
Achieving Point in Time Recovery
Postgres also generates Write Ahead Log (WAL) files, which can be used together with a backed-up file system to recover a database up to any chosen point in time. When disaster strikes, this is one of the best options for recreating your database up to the point right before the unfortunate happens. This greatly minimizes Recovery Point Objective (RPO) along the way. Even better, tools such as WAL-G are readily available to simplify the steps involved in setting this up.
All in all, logical and physical backups are generated differently from one another. Neither has an advantage over the other. Depending on your needs, each brings unique uses to the table:
|Simpler way of getting started with backups.||Better way of handling backups for larger database clusters.|
|Using it to migrate between different major versions of Postgres.||Using it for Point in Time Recovery.|
|Having the option to back up a single database.|