Article Preview

COLUMN

Column

Issue: 15.6 (November/December 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: No description available.
Article Length (in bytes): 11,228
Starting Page Number: 83
Article Number: 15609
Related Web Link(s):

http://www.cybertec.at/postgresql-tablespaces-its-not-so-scary

Excerpt of article text...

In the last two columns we discussed backing up a PostgreSQL database. In this column we will be discussing the options you have for restoring.

As in the previous columns, I will continue to remind everyone that you have not successfully implemented a backup strategy if you have not actually tested the backup (i.e. performed a restore with it). Also, should you see a conflict with whatever I might have written and the official PostgreSQL documentation, then you should absolutely trust the documentation! The flip side to that coin is that regardless of what the documentation says, test your backups!

In the previous two columns we have touched on the two main ways to restore a PostgreSQL database: 1) from a SQL file created by pg_dump and 2) from a binary file also created by pg_dump.

As a reminder, here is the command to restore a PostgreSQL database from a SQL text file that has been created by pg_dump:

psql -d chinook_restore -f chinook_bu.sql

...End of Excerpt. Please purchase the magazine to read the full article.