diff options
| author | Bruce Momjian | 2005-02-08 03:21:02 +0000 |
|---|---|---|
| committer | Bruce Momjian | 2005-02-08 03:21:02 +0000 |
| commit | dc9577967977867f456379af890e4403d7a57171 (patch) | |
| tree | ddd3f1cd85587147dd12de9dece483086479f537 | |
| parent | c76ff4bc4ed07f5b79a1d66772d70a404466ad8c (diff) | |
It seems like most people don't want automatic failover so I am removing
the item:
< o Automatic failover
<
< The proper solution to this will probably the use of a master/slave
< replication solution like Sloney and a connection pooling tool like
< pgpool.
<
| -rw-r--r-- | doc/TODO | 8 |
1 files changed, 1 insertions, 7 deletions
@@ -2,7 +2,7 @@ TODO list for PostgreSQL ======================== Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) -Last updated: Wed Feb 2 12:26:37 EST 2005 +Last updated: Mon Feb 7 22:20:22 EST 2005 The most recent version of this document can be viewed at the PostgreSQL web site, http://www.PostgreSQL.org. @@ -115,12 +115,6 @@ Administration * Allow the PITR process to be debugged and data examined * Allow a warm standby system to also allow read-only queries * Improve replication solutions - o Automatic failover - - The proper solution to this will probably the use of a master/slave - replication solution like Sloney and a connection pooling tool like - pgpool. - o Load balancing You can use any of the master/slave replication servers to use a |