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

Checking for replication slots


Starting from PostgreSQL 9.4, it is also necessary and useful to check for leftover replication slots. The core issue is that if somebody forgets to drop a replication slot, XLOG can accumulate, just as it does in the case of broken archive commands. Therefore, it is essential to keep an eye on useless replication slots (physical as well as logical).

Here is how you can retrieve a list of existing replication slots:

test=# \d pg_replication_slots
View "pg_catalog.pg_replication_slots"
    Column    |  Type   | Modifiers
 --------------+---------+-----------
  slot_name    | name    |
  plugin       | name    |
  slot_type    | text    |
  datoid       | oid     |
  database     | name    |
  active       | boolean |
  xmin         | xid     |
  catalog_xmin | xid     |
  restart_lsn  | pg_lsn  |

To read data from the view, you can simply use TABLE pg_replication_slots.

The main problem is that an administrator has to know about those replication slots that are...

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