|
2 | 2 | TODO list for PostgreSQL |
3 | 3 | ======================== |
4 | 4 | Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us) |
5 | | -Last updated:Wed Feb2 12:26:37 EST 2005 |
| 5 | +Last updated:Mon Feb7 22:20:22 EST 2005 |
6 | 6 |
|
7 | 7 | The most recent version of this document can be viewed at the PostgreSQL web |
8 | 8 | site, http://www.PostgreSQL.org. |
@@ -115,12 +115,6 @@ Administration |
115 | 115 | * Allow the PITR process to be debugged and data examined |
116 | 116 | * Allow a warm standby system to also allow read-only queries |
117 | 117 | * Improve replication solutions |
118 | | -o Automatic failover |
119 | | - |
120 | | - The proper solution to this will probably the use of a master/slave |
121 | | - replication solution like Sloney and a connection pooling tool like |
122 | | - pgpool. |
123 | | - |
124 | 118 | o Load balancing |
125 | 119 |
|
126 | 120 | You can use any of the master/slave replication servers to use a |
|