Create an Account
username: password:
 
  MemeStreams Logo

PostgreSQL: Documentation: Manuals: PostgreSQL 8.3: High Availability, Load Balancing, and Replication

search

Lost
Picture of Lost
My Blog
My Profile
My Audience
My Sources
Send Me a Message

sponsored links

Lost's topics
Arts
Business
Games
Health and Wellness
Home and Garden
Miscellaneous
Current Events
Recreation
Local Information
Science
Society
Sports
Technology

support us

Get MemeStreams Stuff!


 
PostgreSQL: Documentation: Manuals: PostgreSQL 8.3: High Availability, Load Balancing, and Replication
Topic: Technology 2:52 pm EST, Jan  8, 2009

Chapter 25. High Availability, Load Balancing, and Replication

Database servers can work together to allow a second server to take over quickly if the primary server fails (high availability), or to allow several computers to serve the same data (load balancing). Ideally, database servers could work together seamlessly. Web servers serving static web pages can be combined quite easily by merely load-balancing web requests to multiple machines. In fact, read-only database servers can be combined relatively easily too. Unfortunately, most database servers have a read/write mix of requests, and read/write servers are much harder to combine. This is because though read-only data needs to be placed on each server only once, a write to any server has to be propagated to all servers so that future read requests to those servers return consistent results.

PostgreSQL: Documentation: Manuals: PostgreSQL 8.3: High Availability, Load Balancing, and Replication



 
 
Powered By Industrial Memetics
RSS2.0