Article Preview
Buy Now
COLUMN
Column
Issue: 15.4 (July/August 2017)
Author: Craig Boyd
Author Bio: Craig Boyd is currently a data architect for a major fashion retail brand. But in his 20 years of IT experience, he has been everything from a PC Technician, iSeries System Administrator, iSeries Programmer, Sr. Technical Lead, Data Modeler, Data Architect, Oracle DBA, BI Consultant and Solution Architect. He lives in the great state of Texas with his wife and two kids.
Article Description: ageNumber>
Article Length (in bytes): 10,131
Starting Page Number: <
Article Number: 15409
Related Link(s): None
Excerpt of article text...
Hello All! Last time we talked about database backup best practices and briefly touched on using
pg_dump
for backing up your PostgreSQL database. In this article we are going to take a deeper look into pg_dump and how it can be used to back up your PostgreSQL database.If you remember the command to perform a simple backup from the last article was:
pg_dump -d myDatabase -U craig > myDatabase_bu.sql
As a reminder from the previous article you can run this command while the database is up and running. It will take a backup of all the structures as well as the data. The database you are backing up can be noted with the "-d" option or if you just pass the name of the database as the first parameter that works fine too. I personally prefer having the "-d" option since it makes it clear what is being referenced.
...End of Excerpt. Please purchase the magazine to read the full article.