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

Using Londiste to replicate data


The pgq queue is the backbone of a replication tool called Londiste. The idea of Londiste is to have a mechanism that is more simplistic and easier to use than, say, Slony. If you use Slony in a large installation, it is very easy for a problem on one side of the cluster to cause some issues at some other point. This was especially true many years ago when Slony was still fairly new.

The main advantage of Londiste over Slony is that in the case of Londiste replication, there will be one process per "route." So, if you replicate from A to B, this channel will be managed by one Londiste process. If you replicate from B to A or A to C, these will be separate processes, and they will be totally independent of each other. All channels from A to somewhere might share a queue on the consumer, but the transport processes themselves will not interact. There is some beauty in this approach because if one component fails, it is unlikely to cause additional problems....

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