© 2ndQuadrant Limited 2010
Managing
PostgreSQL
Replication
© 2ndQuadrant Limited 2010
Who Am I?
• Simon Riggs
• Major Developer on PostgreSQL project
• CTO, 2ndQuadrant
© 2ndQuadrant Limited 2010
Replication Use Cases
• High Availability
• Scalability
• Protection
• Total Cost of
Ownership
• Exploiting success
© 2ndQuadrant Limited 2010
Replication Mechanisms
• Trigger-based replication
– User space solution
• Log-based replication
– Integrated development
© 2ndQuadrant Limited 2010
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
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
WAL Sender
© 2ndQuadrant Limited 2010
WAL Receiver
© 2ndQuadrant Limited 2010
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
Capabilities
• High Performance
• Integrated
• Ease of Use
• Query Access
• Relay
• Selectivity
• Query Farm
© 2ndQuadrant Limited 2010
Capabilities with Tools
• High Performance
• Integrated
• Ease of Use
• Query Access
• Relay
• Selectivity
• Query Farm
© 2ndQuadrant Limited 2010
Repmgr
© 2ndQuadrant Limited 2010
Repmgr
• Simplify standby management
• Monitor replication delays
• Provide feedback mechanisms
© 2ndQuadrant Limited 2010
Future: Sync Replication (9.1)
• User-controlled robustness
• High performance design
• Simplicity
• Additional flexibility through registration
© 2ndQuadrant Limited 2010
Future: Loose Coupling
• Allows distributed database
• High Availability and Disaster Recovery
• No shared resources – better scalability
• “Cellular” approach
© 2ndQuadrant Limited 2010
PostgreSQL Books
• http://www.2ndQuadrant.com/books/

Managing replication of PostgreSQL, Simon Riggs

  • 1.
    © 2ndQuadrant Limited2010 Managing PostgreSQL Replication
  • 2.
    © 2ndQuadrant Limited2010 Who Am I? • Simon Riggs • Major Developer on PostgreSQL project • CTO, 2ndQuadrant
  • 3.
    © 2ndQuadrant Limited2010 Replication Use Cases • High Availability • Scalability • Protection • Total Cost of Ownership • Exploiting success
  • 4.
    © 2ndQuadrant Limited2010 Replication Mechanisms • Trigger-based replication – User space solution • Log-based replication – Integrated development
  • 5.
    © 2ndQuadrant Limited2010 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
  • 6.
    © 2ndQuadrant Limited2010 Streaming Replication (9.0) • Efficient real-time “log shipping” • Master → Slave replication using full security • Multiple concurrent slaves • Robust bi-modal design
  • 7.
    © 2ndQuadrant Limited2010 WAL Sender
  • 8.
    © 2ndQuadrant Limited2010 WAL Receiver
  • 9.
    © 2ndQuadrant Limited2010 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
  • 10.
    © 2ndQuadrant Limited2010 Capabilities • High Performance • Integrated • Ease of Use • Query Access • Relay • Selectivity • Query Farm
  • 11.
    © 2ndQuadrant Limited2010 Capabilities with Tools • High Performance • Integrated • Ease of Use • Query Access • Relay • Selectivity • Query Farm
  • 12.
  • 13.
    © 2ndQuadrant Limited2010 Repmgr • Simplify standby management • Monitor replication delays • Provide feedback mechanisms
  • 14.
    © 2ndQuadrant Limited2010 Future: Sync Replication (9.1) • User-controlled robustness • High performance design • Simplicity • Additional flexibility through registration
  • 15.
    © 2ndQuadrant Limited2010 Future: Loose Coupling • Allows distributed database • High Availability and Disaster Recovery • No shared resources – better scalability • “Cellular” approach
  • 16.
    © 2ndQuadrant Limited2010 PostgreSQL Books • http://www.2ndQuadrant.com/books/