Difference between revisions of "Pgpool-II 4.2 development"

From pgpool Wiki
Jump to: navigation, search
Line 122: Line 122:
 
| Hoshiai
 
| Hoshiai
 
|[https://www.pgpool.net/pipermail/pgpool-hackers/2019-October/003460.html [pgpool-hackers: 3460]]
 
|[https://www.pgpool.net/pipermail/pgpool-hackers/2019-October/003460.html [pgpool-hackers: 3460]]
 +
|
 +
|-style="background:white"
 +
| 012
 +
| [FEATURE] Implement log process
 +
| 2019/11/01
 +
|
 +
|
 +
|
 +
|
 +
|
 
|
 
|
 
|-style="background:white"
 
|-style="background:white"

Revision as of 02:28, 1 November 2019

Last update: 2019/11/01

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 Priority Implementation Person in charge Overview Status
001 [FEATURE] Cert authentication between Pgpool-II and PostgreSQL
002 [FEATURE] Add new child if it goes down 2015/09/03 - Low Small pgpool-hackers:1034
003 [FEATURE] Make PCP set configuration command public
004 [FEATURE] Seamless Application Failover Similar to Oracle's "Transparent Application Failover".
005 [FEATURE] Enhancing pool_process and pool_pools 2018/02/13 Low Small [pgpool-hackers: 2721]
006 [FEATURE] Support more prefix for query routing (similar to NO LOAD BALANCE) [pgpool-hackers: 2721]
007 [FEATURE] Support for LDAP authentication 2018/11/29 High Medium Usama
008 [FEATURE] Add IPv6 sppport for Pgpool-II 2019/01/17 Low Ishii
009 [FEATURE] Fault injection for watchdog 2019/09/18 High Medium Ishii [pgpool-hackers: 3434]
010 [FEATURE] using volatility categories to determine whether a function is read only or not 2019/09/19 [pgpool-hackers: 3438]
011 [FEATURE] add the process status of pgpool for extended query 2019/10/17 Hoshiai [pgpool-hackers: 3460]
012 [FEATURE] Implement log process 2019/11/01
201 Feature Agreement
202 Feature Freeze
202 Code Freeze