Weitere ähnliche Inhalte
Ähnlich wie Managing replication of PostgreSQL (Simon Riggs)
Ähnlich wie Managing replication of PostgreSQL (Simon Riggs) (20)
Kürzlich hochgeladen (20)
Managing replication of PostgreSQL (Simon Riggs)
- 1. Managing
PostgreSQL
Replication
© 2ndQuadrant Limited 2010
- 2. Who Am I?
• Simon Riggs
• Major Developer on PostgreSQL project
• CTO, 2ndQuadrant
© 2ndQuadrant Limited 2010
- 3. Replication Use Cases
• High Availability • Protection
• Total Cost of
• Scalability Ownership
• Exploiting success
© 2ndQuadrant Limited 2010
- 4. Replication Mechanisms
• Trigger-based replication
– User space solution
• Log-based replication
– Integrated development
© 2ndQuadrant Limited 2010
- 5. Log Shipping Developments
• 8.0 – Point in Time Recovery, Full WAL info
• 8.2 – Restartable Recovery, Log Switching,
Streaming API
• 8.3 – Full Page Optimization, pg_standby
• 8.4 – BgWriter during Recovery
• 9.0 – Streaming Replication
Hot Standby
© 2ndQuadrant Limited 2010
- 6. Streaming Replication (9.0)
• Efficient real-time “log shipping”
• Master → Slave replication using full security
• Multiple concurrent slaves
• Robust bi-modal design
© 2ndQuadrant Limited 2010
- 9. Hot Standby
• Read-only access while “in recovery”
• Equivalent of Oracle 11g Active Data Guard
• Load balanced read scalability
• Query off-load from main write node
• Multiple highly available standby nodes
© 2ndQuadrant Limited 2010
- 10. Capabilities
• High Performance
• Integrated
• Ease of Use
• Query Access
• Relay
• Selectivity
• Query Farm
© 2ndQuadrant Limited 2010
- 11. Capabilities with Tools
• High Performance
• Integrated
• Ease of Use
• Query Access
• Relay
• Selectivity
• Query Farm
© 2ndQuadrant Limited 2010
- 13. Repmgr
• Simplify standby management
• Monitor replication delays
• Provide feedback mechanisms
© 2ndQuadrant Limited 2010
- 14. Future: Sync Replication (9.1)
• User-controlled robustness
• High performance design
• Simplicity
• Additional flexibility through registration
© 2ndQuadrant Limited 2010
- 15. Future: Loose Coupling
• Allows distributed database
• High Availability and Disaster Recovery
• No shared resources – better scalability
• “Cellular” approach
© 2ndQuadrant Limited 2010
- 16. PostgreSQL Books
• http://www.2ndQuadrant.com/books/
© 2ndQuadrant Limited 2010
