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

Making use of replication slots


In PostgreSQL 9.4, a major new feature called "replication slots" has been introduced. The idea is to give users and tools alike a chance to connect to the transaction log stream in a standard way and consume data.

Basically, two types of replication slots exist:

  • Physical replication slots

  • Logical replication slots

The following two sections describe those two types of replication slots in detail.

Physical replication slots

Physical replication slots are an important new feature of PostgreSQL 9.4. The idea is that a client can create a replication slot to make sure that the server only discards what has really made it to the client. Remember that in PostgreSQL, the transaction log is normally recycled as soon as a certain amount of new XLOG has been created. To the streaming replication slaves or some other clients, this can turn out to be disastrous, because if the slave/client cannot consume the transaction log fast enough or if there is simply not enough bandwidth...

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