The documentation describes pg_dump as: “pg_dump is a utility for backing up a PostgreSQL database”Īnd the pg_dumpall documentation: “pg_dumpall is a utility for writing out (“dumping”) all PostgreSQL databases of a cluster into one script file.” Backing up a Database and/or Table(s) More likely, a single workstation/development environment should benefit the most. That being said, this blog post is not targeted at a production environment. Instead, I’ll look at those examples I can apply best, to my personal development/learning environment. Covering them all individually in one blog post would be next to impossible.

PostgreSQL has pg_dump and pg_dumpall out of the box.īoth present numerous customization and structuring options. Most DBMS’s provide some means of built-in backup utilities. Operating on the notion that nothing can happen to your data is a fallacy.

Let’s face it, without them, you basically have nothing. That applies to database backups as well. I’m a firm believer in an old saying I’ve heard: “ It’s better to have it and not need it than to need it and not have it.“ We should be prepared for the event that our data becomes corrupted or lost. Lost or inaccessible data could possibly equate to lost customers.ĭatabase backups should be at the forefront of daily operations and tasks. Availability, consistent state, and durability are top priorities for keeping customers and end-users satisfied. Businesses and services deliver value based on data.

Postgresql commands with examples