|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.3 2006/11/2021:26:22 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.4 2006/11/2022:07:56 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability and Load Balancing</title> |
|
143 | 143 | </varlistentry> |
144 | 144 |
|
145 | 145 | <varlistentry> |
146 | | - <term>Statement-Based Replication</term> |
| 146 | + <term>Statement-Based Replication Middleware</term> |
147 | 147 | <listitem> |
148 | 148 |
|
149 | 149 | <para> |
150 | | - In statement-based replication, a program intercepts every SQL |
151 | | - query and sends it to all servers. Each server operates |
152 | | - independently. Read-only queries can be sent to a single server |
153 | | - because there is no need for all servers to process it. |
| 150 | + With statement-based replication middleware, a program intercepts |
| 151 | + every SQL query and sends it to all servers. Each server |
| 152 | + operates independently. Read-only queries can be sent to a |
| 153 | + single server because there is no need for all servers to |
| 154 | + process it. |
154 | 155 | </para> |
155 | 156 |
|
156 | 157 | <para> |
|