Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit dc95779

Browse files
committed
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. <
1 parent c76ff4b commit dc95779

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

doc/TODO

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
TODO list for PostgreSQL
33
========================
44
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
5-
Last updated: Wed Feb 2 12:26:37 EST 2005
5+
Last updated: Mon Feb 7 22:20:22 EST 2005
66

77
The most recent version of this document can be viewed at the PostgreSQL web
88
site, http://www.PostgreSQL.org.
@@ -115,12 +115,6 @@ Administration
115115
* Allow the PITR process to be debugged and data examined
116116
* Allow a warm standby system to also allow read-only queries
117117
* 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-
124118
o Load balancing
125119

126120
You can use any of the master/slave replication servers to use a

0 commit comments

Comments
 (0)