Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
PostgreSQL Replication, Second Edition

You're reading from  PostgreSQL Replication, Second Edition

Product type Book
Published in Jul 2015
Publisher
ISBN-13 9781783550609
Pages 322 pages
Edition 1st Edition
Languages
Toc

Table of Contents (22) Chapters close

PostgreSQL Replication Second Edition
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Understanding the Concepts of Replication 2. Understanding the PostgreSQL Transaction Log 3. Understanding Point-in-time Recovery 4. Setting Up Asynchronous Replication 5. Setting Up Synchronous Replication 6. Monitoring Your Setup 7. Understanding Linux High Availability 8. Working with PgBouncer 9. Working with pgpool 10. Configuring Slony 11. Using SkyTools 12. Working with Postgres-XC 13. Scaling with PL/Proxy 14. Scaling with BDR 15. Working with Walbouncer Index

Archiving the transaction log


After taking a look at the big picture, we can see how things can be put to work.

The first thing you have to do when it comes to Point-in-time Recovery is archive the XLOG. PostgreSQL offers all the configuration options related to archiving through postgresql.conf.

Let us see step by step what has to be done in postgresql.conf to start archiving:

  1. First of all, you should turn archive_mode on.

  2. In the second step, you should configure your archive_command. The archive_command is a simple shell, and it needs just two parameters to operate properly:

    • %p: This is a placeholder representing the XLOG file that should be archived, including its full path (source).

    • %f: This variable holds the name of XLOG without the path pointing to it.

Let's set up archiving now. To do so, we should create a place to put the XLOG. Ideally, the XLOG is not stored on the same hardware as the database instance you want to archive. For the sake of this example, we assume that we want to copy...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime