mirror of
https://github.com/postgres/postgres.git
synced 2025-12-24 06:01:07 +03:00
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. <
This commit is contained in:
8
doc/TODO
8
doc/TODO
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user