Search icon
Subscription
0
Cart icon
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
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

Table of Contents (22) Chapters

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

Checking your archive


If you are planning to use PITR or if you want to use an XLOG archive to assist in your streaming setup, various things can go wrong, for example:

  • Pushing of the XLOG might fail

  • Cleanup of the archive might fail

Of course, there are countless other things that can go wrong. However, in this chapter, our goal is to focus on the most common issues people face.

Checking archive_command

A failing archive_command variable might be one of the greatest showstoppers in your setup. The purpose of archive_command is to push XLOG to some archive and store the data there. But what happens if those XLOG files cannot be pushed for some reason?

The answer is quite simple: the master has to keep these XLOG files to ensure that no XLOG files can be lost. There must always be an uninterrupted sequence of XLOG files. Even if a single file in the sequence of files is missing, your slave won't be able to recover anymore. For example, if your network has failed, the master will accumulate those...

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}