Difference between revisions of "Pgpool-II 4.1 development"

From pgpool Wiki
Jump to: navigation, search
Line 42: Line 42:
 
| Ahsan
 
| Ahsan
 
| Similar to Oracle's "Transparent Application Failover".
 
| Similar to Oracle's "Transparent Application Failover".
 +
|
 +
|-style="background:white"
 +
| 005
 +
| Proposal: Enhancing pool_process and pool_pools
 +
| 2018/02/13
 +
|
 +
| Tatsuo
 +
| http://www.sraoss.jp/pipermail/pgpool-hackers/2018-February/002721.html
 
|  
 
|  
 
|-style="background:white"
 
|-style="background:white"

Revision as of 06:41, 5 October 2018

Last update: 2018/10/05 (gray items are done, yellow items are behind schedule, orange items are new features for 4.0, and pink items are other TODO)

Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.

ID Registered/start Date Target Date Person in charge Overview Status
001 [FEATURE] Cert authentication between Pgpool-II and PostgreSQL
002 pgpool-hackers:1034 2015/09/03 - Usama add new child if it goes down [Feature: small]
003 Make PCP set configuration command public 2016/2/15 - Usama - [Feature: small]
004 New feature candidate: Seamless Application Failover 2017/3/23 Ahsan Similar to Oracle's "Transparent Application Failover".
005 Proposal: Enhancing pool_process and pool_pools 2018/02/13 Tatsuo http://www.sraoss.jp/pipermail/pgpool-hackers/2018-February/002721.html
002
101
102
201 Feature Agreement
202 Feature Freeze
202 Code Freeze