View source for pgpool-II 3.6 development

Last update: 2016/4/8 (gray items are done, yellow items are behind schedule)

{| class="wikitable"
! 
! ID
! Registered/start Date
! Target Date
! Person in charge
! Overview
! Status
|- style="background:silver"
| 1
| pgpool-general:3907
| 2015/08/02
| 2015/10/28
| Usama
| watchdog info
| Done in [pgpool-general: 4452]
|-
| 2
| pgpool-general:3923
| 2015/08/06
| -
| Tatsuo
| pgpool_status
| needs discussion, postpone to 3.6
|-
| 3
| pgpool-hackers:994
| 2015/08/05
| -
| Tatsuo
| connect to necessary DB nodes
| proposal, feedback, postpone to 3.6
|-
| 4
| pgpool:330
| 2015/08/12
| -
| Ahsan, Tatsuo
| mesuring pgpool-II overhead
| in progress, Tatsuo will review the result, postpone to 3.6
|-
| 5
| pgpool-hackers:1034
| 2015/09/03
| -
| -
| add new child if it goes down
| need to assign, postpone to 3.6
|-
| 6
| pgpool-general:4016
| 2015/09/02
| -
| -
| deal with pg_terminate_backend
| need to assign or expecting patches from user, postpone to 3.6
|-
| 7
| Import PostgreSQL 9.6 parser
| 2016/2/15
| -
| -
| -
| Start after PostgreSQL 9.6 beta released
|-
| 8
| Add SET command
| 2016/2/15
| 2016/4/4
| Usama
| -
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.
|-style="background:silver"
| 9-1
| Convert the pgpool documentation to SGML
| 2016/2/15
| 2016/2/15
| Usama
| Tool set porting work time estimate
| Estimating work hours to determine the shedule. He estimated as "3.5D".
|- style="background:silver"
| 9-2
| Convert the pgpool documentation to SGML
| 2016/2/16
| 2016/2/19
| Usama
| Tool set porting
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files
|- style="background:silver"
| 9-3
| Convert the pgpool documentation to SGML
| 2016/2/26
| 2016/2/29
| Tatsuo
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs
|
|-
| 9-4
| Convert the pgpool documentation to SGML
| 2016/2/27
|
|
| Create/migrate actual pgpool-II document in SGML format
|
|-
| 10
| Make PCP set configuration command public 
| 2016/2/15
| -
| Usama
| -
| 
|-
| 11
| Keep current session alive in-case of failover
| 2016/2/15
| 2016/3/31
| Tatsuo
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html
| Proposal already posted
|- style="background:silver"
| 12
| Yet another stuck connection problem
| 2016/2/19
| 2016/2/23
| Usama
|
| pgpool-general: 4457
|-
|-
| 13
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS
| 2016/2/26
| 
| Usama
|
| 
|-
| 14
| Allow to use multiple pgpool-II instances with in-memory query cache enabled
| 2016/3/4
|
|
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery
| 
|-
|-
| 15
| Health-check timeout for each backend node
| 2016/3/4
|
|
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node
| 
|-
|- style="background:silver"
| 16
| Worker Processes Exit and Are Not Re-spawned
| 2016/3/7
|
| Usama
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html
| 
|-
|--style="background:silver"
| 17
| Extended query hangs
| 2016/2/22
| 2016/3/27
| Tatsuo
|http://www.pgpool.net/mantisbt/view.php?id=167
|Fix confirmed (2016/3/30).
|-
|-style="background:silver"
| 18
| Buildfarm not working
| 2016/3/16
|
| Yugo
|
| Should be fixed as soon as possible. It turned out that it was caused by disk full.
|-style="background:silver"
| 19
| failback_command finishes,pgpool-II DONNOT restart all child processes
| 2016/3/18
|
| Usama
|http://www.pgpool.net/mantisbt/view.php?id=172
|
|-style="background:silver"
| 20
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node
| 2016/3/18
|
| Tatsuo
|http://www.pgpool.net/mantisbt/view.php?id=174
|
|-
| 21
| find_primay_node fails to find the primary node
| 2016/3/22
|
| Tatsuo
|pgpool-general: 4560
|Waiting for feedback.
|-
| 22
| kind mismatch among backends with COMMIT;
| 2016/3/23
|
| Usama
|pgpool-general: 4565
|Waiting for feedback.
|-
| 23
| Error with JDBC memory_cache_enabled = on
| 2016/3/22
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=152
|Waiting for a feedback
|-style="background:silver"
| 24
| Enironment Variable PG_CONFIG Ignored
| 2016/3/23
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=178
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.
|-style="background:silver"
| 25
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS
| 2016/3/23
|
| Usama
| http://www.pgpool.net/mantisbt/view.php?id=179
| Responded back, nothing to be done for that
|-style="background:silver"
| 26
| regression test failure with 004.watchdog
| 2016/3/22
|
| Usama
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac
| Usama found that this was caused my race condition while writing to a log file. Tatsuo fixed this by redirecting process output to cat command.
|-style="background:silver"
| 27
| Pgpool child hangs with full cpu load after permission error message from backend
| 2016/3/24
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=182
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29
|-
| 28
| Online recovery: existing connections did not close in 90 sec.
| 2016/3/23
|
| Tatsuo
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)
|
|-style="background:silver"
| 29
| Pgppol not sending query error back to client
| 2016/3/25
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=183
| Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28
|-style="background:silver"
| 30
| PGPoolII-3.5 : segfault during pcp_recovery
| 2016/3/23
| 2016/4/4
| Usama
| pgpool-general: 4569
| fixed  commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9
|-style="background:silver"
| 31
| pgpool-II minor releases
| 
| 2016/4/4
| Yugo
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1
|
|-style="background:white"
| 32
| plugs out the network cable，the pgpool will not work。
| 2016/3/28
|
| Usama
| http://www.pgpool.net/mantisbt/view.php?id=185
| 
|-style="background:silver"
| 33
| Hibernate + Pgpool-II Connection Failure
| 2016/3/18
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=175
| Fix confirmed (in 3.5.1)
|-style="background:white"
| 34
| What is the execution order of ‘follow_master_command' and 'failover_command'?
| 2016/3/19
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=176
| Waiting for feedback
|-style="background:white"
| 35
| Pgpool stops accepting connections when Postgresql slave goes down
| 2016/3/20
|
| Usama
| http://www.pgpool.net/mantisbt/view.php?id=177
|
|-
| 36
| pcp_proc_count truncates PIDs over 5 characters long
| 2016/4/6
|
| Peng
| http://www.pgpool.net/mantisbt/view.php?id=188
| In progress
|-
| 37
| pgpool web console gets pgpool.conf parameters incorrectly
| 2016/4/7
|
| Usama
| http://www.pgpool.net/mantisbt/view.php?id=158
| assigned [Pgpool:1102] Bug 158
|-
| 38
| Always PostgreSQL1 node is down frequently from PGpool console
| 2016/4/7
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=161
| feedback
|-
| 39
| Connections not released if client exit ungracefully
| 2016/4/7
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=163
| feedback
|-
| 40
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism
| 2016/4/7
|
| Nozomi
| http://www.pgpool.net/mantisbt/view.php?id=187
| assigned 
|-
| 41
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off
| 2016/4/8
|
| Tatsuo
| http://www.pgpool.net/mantisbt/view.php?id=189
| assigned 
|-style="background:yellow"
| 100
| Platform freeze
| 2016/2/19
| 2016/3/15
| -
| -
| All the new platforms that we want to support and add to BF should be decided by this date. It seems we will not add any new supported platforms.
|-style="background:yellow"
| 101
| Feature requirement freeze
| 2016/2/19
| 2016/3/15
| -
| -
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date 
|-
| 102
| Feature Freeze
| 2016/2/19
| 2016/7/30
| -
| -
| Ensure all the agreed upon features are committed to master by this date. This should be feature complete and we should only focus on bug fixed after this point.
|-
| 103
| Code Freeze
| 2016/2/19
| 2016/8/31
| -
| -
| At-least one month period between feature and code freeze to ensure all new features are stable and critical bugs are fixed by this date.
|-
| 104
| pgpool-II 3.6 beta1
| 2016/2/19
| 2016/8/31
| -
| -
| First Beta
|-
| 105
| pgpool-II 3.6 RC1
| 2016/2/19
| 2016/9/30
| -
| -
| One month after beta1
|-
| 106
| pgpool-II 3.6.0 official release
| 2016/2/19
| 2016/10/30
| -
| -
|
|}