Re: PostgreSQL Backup Booklet - Mailing list pgsql-general

From Carlos Mennens
Subject Re: PostgreSQL Backup Booklet
Date
Msg-id CAAQLLO5-wYboVvQ6KqzJM5yTv10sQy6tQENkiB-mzoy0CH1DZw@mail.gmail.com
Whole thread Raw
In response to PostgreSQL Backup Booklet  (Shaun Thomas <sthomas@optionshouse.com>)
List pgsql-general
Based on Amazon reviews and others in the PG community, I would 100% get something like this. High Availability / Fail Over are my biggest concerns with PostgreSQL Database.

Thanks so much for sharing and good luck!!!


On Wed, Apr 3, 2013 at 10:09 AM, Shaun Thomas <sthomas@optionshouse.com> wrote:
Hey!

So, Packt approached me a few months ago and asked me to put together a very basic series of short step-by-step instructions on backing up PostgreSQL. The title is "Instant PostgreSQL Backup and Restore How-to."

I tried to cover all of the basic approaches used by most admins, and I tested it on a guy at work who's a SQL Server DBA but recently took over care and feeding of a PG database. He said it was easier to understand than the documentation, at least for just getting everything working and sorting out more advanced details later.

I know it's not exactly Greg Smith's performance book, but I'm glad to contribute how I can. I'm not entirely sure it's worth adding to the book page:

http://www.postgresql.org/docs/books/

But if it is, I'll provide any help or extra information necessary. If anyone has questions, I'm here to answer them. :)

--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
Carlos Mennens

pgsql-general by date:

Previous
From: Shaun Thomas
Date:
Subject: PostgreSQL Backup Booklet
Next
From: Kevin Grittner
Date:
Subject: Re: PostgreSQL: CPU utilization creeping to 100%