mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rename replication section "High Availability and Load Balancing".

Browse Source
This commit is contained in:
Bruce Momjian 2006-11-17 16:38:44 +00:00
parent cc9698254c
commit e1693e514c
3 changed files with 27 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/filelist.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/filelist.sgml,v 1.48 2006/10/26 15:26:54 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/filelist.sgml,v 1.49 2006/11/17 16:38:44 momjian Exp $ -->
<!entity history SYSTEM "history.sgml"> <!entity history SYSTEM "history.sgml">
<!entity info SYSTEM "info.sgml"> <!entity info SYSTEM "info.sgml">
@ -34,7 +34,7 @@
<!entity charset SYSTEM "charset.sgml"> <!entity charset SYSTEM "charset.sgml">
<!entity client-auth SYSTEM "client-auth.sgml"> <!entity client-auth SYSTEM "client-auth.sgml">
<!entity diskusage SYSTEM "diskusage.sgml"> <!entity diskusage SYSTEM "diskusage.sgml">
<!entity failover SYSTEM "failover.sgml"> <!entity high-availability SYSTEM "high-availability.sgml">
<!entity installation SYSTEM "installation.sgml"> <!entity installation SYSTEM "installation.sgml">
<!entity installw SYSTEM "install-win32.sgml"> <!entity installw SYSTEM "install-win32.sgml">
<!entity maintenance SYSTEM "maintenance.sgml"> <!entity maintenance SYSTEM "maintenance.sgml">

43
doc/src/sgml/failover.sgml → doc/src/sgml/high-availability.sgml
View File

@ -1,35 +1,38 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.13 2006/11/17 13:29:53 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.1 2006/11/17 16:38:44 momjian Exp $ -->
<chapter id="failover"> <chapter id="high-availability">
<title>Failover, Replication, Load Balancing, and Clustering Options</title> <title>High Availability and Load Balancing</title>
<indexterm><primary>high availability</></>
<indexterm><primary>failover</></> <indexterm><primary>failover</></>
<indexterm><primary>replication</></> <indexterm><primary>replication</></>
<indexterm><primary>load balancing</></> <indexterm><primary>load balancing</></>
<indexterm><primary>clustering</></> <indexterm><primary>clustering</></>
<indexterm><primary>data partitioning</></>
<para> <para>
Database servers can work together to allow a second server to Database servers can work together to allow a second server to
quickly take over if the primary server fails (failover), or to quickly take over quickly if the primary server fails (high
allow several computers to serve the same data (load balancing). availability), or to allow several computers to serve the same
Ideally, database servers could work together seamlessly. Web data (load balancing). Ideally, database servers could work
servers serving static web pages can be combined quite easily by together seamlessly. Web servers serving static web pages can
merely load-balancing web requests to multiple machines. In be combined quite easily by merely load-balancing web requests
fact, read-only database servers can be combined relatively easily to multiple machines. In fact, read-only database servers can
too. Unfortunately, most database servers have a read/write mix be combined relatively easily too. Unfortunately, most database
of requests, and read/write servers are much harder to combine. servers have a read/write mix of requests, and read/write servers
This is because though read-only data needs to be placed on each are much harder to combine. This is because though read-only
server only once, a write to any server has to be propagated to data needs to be placed on each server only once, a write to any
all servers so that future read requests to those servers return server has to be propagated to all servers so that future read
consistent results. requests to those servers return consistent results.
</para> </para>
<para> <para>
This synchronization problem is the fundamental difficulty for servers This synchronization problem is the fundamental difficulty for
working together. Because there is no single solution that eliminates servers working together. Because there is no single solution
the impact of the sync problem for all use cases, there are multiple that eliminates the impact of the sync problem for all use cases,
solutions. Each solution addresses this problem in a different way, and there are multiple solutions. Each solution addresses this
minimizes its impact for a specific workload. problem in a different way, and minimizes its impact for a specific
workload.
</para> </para>
<para> <para>

4
doc/src/sgml/postgres.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/postgres.sgml,v 1.79 2006/10/26 15:26:54 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/postgres.sgml,v 1.80 2006/11/17 16:38:44 momjian Exp $ -->
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [
@ -151,7 +151,7 @@
&charset; &charset;
&maintenance; &maintenance;
&backup; &backup;
&failover; &high-availability;
&monitoring; &monitoring;
&diskusage; &diskusage;
&wal; &wal;