https://pgpool.net/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=Usama
pgpool Wiki - User contributions [en]
2026-05-04T06:17:30Z
User contributions
MediaWiki 1.43.3
https://pgpool.net/mediawiki/index.php?title=Pgpool-II_4.1_development&diff=3143
Pgpool-II 4.1 development
2019-10-03T20:45:36Z
<p>Usama: </p>
<hr />
<div>Last update: 2019/10/02<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
Red items are open items for Pgpool-II 4.1.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Priority<br />
! Implementation<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:orange"<br />
| 007<br />
| [FEATURE] shared relation cache<br />
| 2018/11/20<br />
| 2019/02/29<br />
| High<br />
| Large<br />
| Hoshiai<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2018-November/003124.html [pgpool-hackers: 3124]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=46917d5458a82c75e98b247a74b7ee1827666159 commit]<br />
|-style="background:beige"<br />
| rowspan="3" | 008<br />
| [FEATURE] Enhance performance: performance regression test<br />
| 2018/11/20<br />
| <br />
| High<br />
| Small<br />
| Usama<br />
|<br />
| <br />
|-style="background:orange"<br />
| [FEATURE] Enhance performance: performance for simple query (especially for of the large<br />
INSERT and UPDATE statements)<br />
| 2018/11/20<br />
|<br />
|<br />
| XLarge<br />
| Usama<br />
|<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=310c5c4a289cbe6cee01abef7d2e7bc3550944fb commit]<br />
|-style="background:orange"<br />
| [FEATURE] Enhance performance: performance for extended query <br />
| 2019/01/17<br />
|<br />
|<br />
| <br />
| Ishii<br />
| <br />
| (1) Enhance performance for COPY XXX TO STDOUT (both for simple and extended query): [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=702f7c86f9b8f82f61e47235505715891ffe1b23 commit] <br> <br />
(2) Enhance performance for extended query message: <br> [https://www.pgpool.net/pipermail/pgpool-hackers/2019-February/003230.html [pgpool-hackers: 3230]] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=778f611e201d6df88ed90d01e49af77daf9f2926 commit] <br> (3) Eliminate select(2) calls in certain cases to enhance performance in simple and extended query: <br> [https://www.pgpool.net/pipermail/pgpool-hackers/2019-February/003247.html [pgpool-hackers: 3247]] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=cf5fe7eb89a11e3ada3833343c7ed6551ce7c662 commit]<br />
|-style="background:orange"<br />
| rowspan="2" | 009<br />
| [Documentation] Review and improve the current document<br />
| 2018/11/20<br />
| <br />
| High<br />
| Extra Large<br />
| Hoshiai<br />
|<br />
| [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=ea1998b7350de6882bea25fc3634c4f7673adbde commit1][https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=5f259f3b5e1b56763677d0b7aa736eb8772a8968 commit2][https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=b69e94e97ed4226e335e85f01bfc373c8e11db8f commit3] <br><br />
[https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=b69e94e97ed4226e335e85f01bfc373c8e11db8f commit4] <br />
[https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=c013bad08e67bd53d39a66835c67bc93d334d72b commit5]<br />
[https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=6d3939dac4d76eed5dcd1867fb16e8bc8215dc61 commit6]<br />
|-style="background:orange"<br />
| [Documentation] Update the examples to latest version.<br />
| 2018/11/20<br />
| <br />
| High<br />
| <br />
| Peng<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=0c9f716714dce156fe74469a933046b39896a072 commit] [http://www.pgpool.net/docs/latest/en/html/example-cluster.html doc] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=69c6a4cd5f49384a1d719e4e784ff84855f00a9d commit]<br />
|-style="background:orange"<br />
| 010<br />
| [FEATURE] Master watchdog sets quarantine state to primary node<br />
| 2018/11/26<br />
| <br />
| Normal<br />
| Small <br />
| Usama<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-March/002756.html [pgpool-hackers: 2756]] <br>[https://www.pgpool.net/pipermail/pgpool-general-jp/2018-March/001503.html [pgpool-general-jp: 1504]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=3922c12c1f8efbc1b5f2e7def1e0ff921aafb989 Commit]<br />
|-style="background:orange"<br />
| 011<br />
| [FEATURE] limiting number of frontends differently<br />
| 2018/11/26<br />
| 2018/12/04<br />
| <br />
| <br />
| Ishii<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-November/003153.html [pgpool-hackers: 3153]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=693a6284cf2dfc2e60d5a2489c9ee5167defc3dc commit]<br />
|-style="background:orange"<br />
| 012 <br />
| [FEATURE] Don't load balance after a SELECT having functions specified in black function list<br />
| 2018/11/29<br />
| 2019/06/30<br />
| Normal<br />
| Small<br />
| Peng<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2018-November/003157.html [pgpool-hackers: 3157]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=3ddf9aa0b20480b22bb5e8fc6097f2eb7cb56994 commit]<br />
|-style="background:orange"<br />
| 014<br />
| [FEATURE] Support for PostgreSQL 12.<br />
| 2018/11/29<br />
| <br />
| High<br />
| Small<br />
| Ishii<br />
| recovery.conf <br> pgpool_setup <br> pgppol-recovery extension<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=fda13a93a1025b498bb2a674fb49406d9e3e509c pgpool-recovery extension] <br> [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=23fb4c1250f0464a867f2ac69006d74f134213e3 pgpool_setup]<br />
|-style="background:orange"<br />
| 015<br />
| [FEATURE] Import PostgreSQL 12 parser.<br />
| 2018/11/29<br />
| 2019/07/31<br />
| High<br />
| Medium<br />
| Peng<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f694283cfd55a52750ce56697af2e5cd1d1da571 commit]<br />
|-style="background:orange"<br />
| 016<br />
| [FEATURE] Statement level load balancing<br />
| 2018/12/06<br />
| 2019/03/31<br />
| High<br />
| Large<br />
| Peng<br />
|<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=1099ba610eef06a9dab6f89486cc52de55ff3ebb commit]<br />
|-style="background:orange"<br />
| 018<br />
| [FEATURE] Add new columns to "show pool_nodes" command<br />
| 2019/04/22<br />
| 2019/04/24<br />
| High<br />
| Medium<br />
| Ishii<br />
| Discussion: [https://www.pgpool.net/pipermail/pgpool-hackers/2019-April/003315.html [pgpool-hackers: 3315]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=35cb1dc2d9d9f4887bd0407f150558660b7826e1 Commit]<br />
|-style="background:orange"<br />
| 019<br />
| [FEATURE][Document] Add new performance section<br />
| <br />
|<br />
| High<br />
| Medium<br />
| Ishii<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=854659a17b958536e80c461d55c9ba0f1032a128 commit]<br />
|-style="background:orange"<br />
| 020<br />
| [FEATURE] auto failback<br />
| 2019/5/23<br />
| 2019/7/5<br />
| <br />
| Medium<br />
| Hoshiai<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-May/003328.html [pgpool-hackers: 3328]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=3e2ecc970864056ff054799cac57ad5b30312c48 commit] <br />
|-style="background:orange"<br />
| 021<br />
| [FEATURE] allow to use md5 password in health_check_password and sr_check_password<br />
| 2019/5/30<br />
| 2019/6/10<br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-May/003334.html [pgpool-hackers: 3334]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=dc9742678dd04719a08a747d40cd4c0781fce49a commit]<br />
|-style="background:orange"<br />
| 022<br />
| [FEATURE] Routing relcache queries to load balance node<br />
| <br />
| <br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-June/003342.html [pgpool-hackers: 3342]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=46986ebc0be77e4b011b94b097789fec9e3f5b0f commit]<br />
|-style="background:orange"<br />
| 023<br />
| [FEATURE] Support ECDH key exchange with SSL<br />
| <br />
| <br />
| <br />
| Medium<br />
| Hoshiai<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=51bc494aaa7fd191e14038204d18effe2efb0ec8 commit1] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f63c260d7e389bc03822721a9d66a0d6c7d22f4b commit2]<br />
|-style="background:orange"<br />
| 024<br />
| [FEATURE] Reduce relcahe queries<br />
| <br />
| <br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-June/003344.html [pgpool-hackers: 3344]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=6282805d4ae3f7a76ed607c0124420b8fe4c8320 commit]<br />
|-style="background:orange"<br />
| 025<br />
| [FEATURE] Eliminate temp table relcahe query<br />
| <br />
| <br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-June/003346.html [pgpool-hackers: 3346]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=7a0471bbcc3ab06a9cab9902d91e5c4c692b3284 commit]<br />
|-style="background:orange"<br />
| 026<br />
| [FEATURE] Add new arguments in pgpool_recovery function and failover_command/failback_command/follow_master_command.<br />
| <br />
| <br />
| <br />
| Small<br />
| Peng<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=ed90a39db3664eb7be85f192f5472cc0b59a2d8f commit]<br />
|-style="background:silver"<br />
| 101<br />
| 0000433: IN (SELECT ...) can not be rewritten in native replication mode<br />
| 2018/10/19<br />
| <br />
| <br />
| <br />
| Peng<br />
| [http://www.pgpool.net/mantisbt/view.php?id=433 bug433]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=d53292592a9808b260171f8569752ca89d7412fc commit] <br>Regression test should be added.<br />
|-style="background:silver"<br />
| 102<br />
| 0000434: Segmentation fault due to a query error and Sync messages in native replication mode<br />
| 2018/10/19<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| [https://www.pgpool.net/mantisbt/view.php?id=434 bug434]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=5e6d598b964ac88f41a18280f6289ca5e78ffad5 commit]<br />
|-style="background:silver"<br />
| 103<br />
| pool_passwd is corrupted.<br />
| 2018/10/22<br />
| <br />
| <br />
| <br />
| Hoshiai, Usama<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-October/003081.html [pgpool-hackers: 3081]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=d48cc28a7b2ac42185b48873608ff876f9298d89 commit]<br />
|-style="background:silver"<br />
| 104<br />
| [pgpool-hackers: 3025] Compile warns<br />
| 2018/10/22<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-August/003025.html [pgpool-hackers: 3025]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bc9119f61b187577d64b63ebffb6f5412202f24f commit]<br />
|-style="background:silver"<br />
| 105<br />
| 0000443: Segmentation fault occurs when a certain Bind message is sent in native replication mode.<br />
| 2018/11/08<br />
| <br />
| <br />
| <br />
| Peng<br />
| [https://www.pgpool.net/mantisbt/view.php?id=443 bug443]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=1d8d03237a2ad507f8f1fb8fb0c84b3084f57cdc commit]<br />
|-style="background:silver"<br />
| 106<br />
| 0000444: pgpool does not take into account parameters order in startup packet<br />
| 2018/11/13<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| [https://www.pgpool.net/mantisbt/view.php?id=444 bug444]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=ffb998517bb91c512b77fbe1ca8ee331e492f131 commit]<br />
|-style="background:silver"<br />
| 107<br />
| 0000448: pgpool holds the connections as idle_in_transaction which are timed out due to idle_in_transaction setting on backend nodes<br />
| 2018/11/29<br />
| <br />
| <br />
| <br />
| Ishii<br />
| [https://www.pgpool.net/mantisbt/view.php?id=448 bug448]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=3f5986eee360f12e6a0bb77aa46f95abf5f6bc10 commit]<br />
|-style="background:silver"<br />
| 108<br />
| [pgpool-general: 6351] kind mismatch among backends, savepoint with psqlodbc<br />
| 2018/12/26<br />
| <br />
| <br />
| <br />
| Peng<br />
| [https://www.pgpool.net/pipermail/pgpool-general/2018-December/006409.html [pgpool-general: 6351]]<br />
| <br />
|-style="background:silver"<br />
| 109<br />
| 0000455: watchdog lifecheck process has segfalut in query mode<br />
| 2019/01/21<br />
| <br />
| <br />
| <br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=455<br />
| Done. https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=4cde5da1b416d909d102cfe6878c0cd5189caf86<br />
|-style="background:white"<br />
| 110<br />
| Add regression test for query mode <br />
| 2019/01/21<br />
| <br />
| <br />
| <br />
| Peng<br />
| <br />
| <br />
|-style="background:silver"<br />
| 111<br />
| 0000483: online-recovery is blocked after a child process exits abnormally with replication mode and watchdog<br />
| 2019/04/04 <br />
| <br />
| <br />
| <br />
| Usama<br />
| [https://www.pgpool.net/mantisbt/view.php?id=483 bug483]<br />
| Done [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=c402060814ba9737e9572ba07eef1be7664c9679 commit].<br />
|-style="background:silver"<br />
| 112<br />
| Fix memory leak related to watchdog and auth pointed out by coverity<br />
| 2019/05/22<br />
| <br />
| <br />
|<br />
| Usama<br />
| src/auth/pool_hba.c src/auth/pool_auth.c src/auth/auth-scram.c src/watchdog/watchdog.c src/watchdog/wd_lifecheck.c src/config/pool_config_variable.c<br />
| Done<br />
|-style="background:silver"<br />
| 113<br />
| Fix memory leak related to watchdog and auth pointed out by coverity<br />
| 2019/05/22<br />
| <br />
| <br />
| <br />
| ishii<br />
| other than :src/auth/pool_hba.c src/auth/pool_auth.c src/auth/auth-scram.c src/watchdog/watchdog.c src/watchdog/wd_lifecheck.c src/config/pool_config_variable.c<br />
| <br />
|-style="background:red"<br />
| 114<br />
| [https://www.pgpool.net/pipermail/pgpool-general/2019-August/006730.html pgpool-general: 6672] Query (watchdog split brain)<br />
| 2019/08/16<br />
| <br />
| <br />
| <br />
| Usama<br />
| <br />
| Requested log sent [https://www.pgpool.net/pipermail/pgpool-general/2019-September/006753.html pgpool-general: 6695]<br />
|-style="background:silver"<br />
| 115<br />
| regression test 013.watchdog_failover_require_consensus failed<br />
| 2019/08/14<br />
| <br />
| <br />
| <br />
| Ishii<br />
| <br />
| <br />
|-style="background:red"<br />
| 116<br />
| Doc:Pgpool-II + Watchdog Setup Example (for PostgreSQL 12)<br />
| 2019/09/03<br />
| <br />
| <br />
| <br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 117<br />
| regression test 028. 028.watchdog_enable_consensus_with_half_votes failed<br />
| 2019/09/13<br />
| 2019/09/18<br />
| <br />
| <br />
| Ishii<br />
| <br />
| <br />
|-style="background:silver"<br />
| 118<br />
| 0000545: Quorum lost and not recovered<br />
| 2019/09/09<br />
| <br />
| <br />
| <br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=545<br />
| <br />
|-style="background:red"<br />
| 119<br />
| 0000547: We need to do arping again after recovering from split-brain.<br />
| 2019/09/12<br />
| <br />
| <br />
| <br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=547<br />
| <br />
|-style="background:red"<br />
| 120<br />
| regression test 065.bug152 failed if enable_shared_relcache is on<br />
| 2019/10/02<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| <br />
| <br />
|-style="background:white"<br />
| 201<br />
| Feature Agreement <br />
| <br />
| <br />
| <br />
| <br />
|<br />
|<br />
| <br />
|-style="background:white"<br />
| 202<br />
| Feature Freeze <br />
| <br />
| 2019/08/15<br />
| <br />
| <br />
|<br />
|<br />
| <br />
|-style="background:white"<br />
| 203<br />
| Code Freeze <br />
| <br />
| 2019/08/31<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|<br />
|-style="background:white"<br />
| 204<br />
| Release beta1<br />
| <br />
| 2019/09/06<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|<br />
|-style="background:white"<br />
| 205<br />
| RC Release<br />
| <br />
| 2019/10/4<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|-style="background:white"<br />
| 206<br />
| Official Release<br />
| <br />
| 2019/10/15<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=Pgpool-II_4.1_development&diff=3037
Pgpool-II 4.1 development
2019-08-08T14:50:58Z
<p>Usama: </p>
<hr />
<div>Last update: 2019/08/08<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Priority<br />
! Implementation<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:orange"<br />
| 007<br />
| [FEATURE] shared relation cache<br />
| 2018/11/20<br />
| 2019/02/29<br />
| High<br />
| Large<br />
| Hoshiai<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2018-November/003124.html [pgpool-hackers: 3124]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=46917d5458a82c75e98b247a74b7ee1827666159 commit]<br />
|-style="background:beige"<br />
| rowspan="3" | 008<br />
| [FEATURE] Enhance performance: performance regression test<br />
| 2018/11/20<br />
| <br />
| High<br />
| Small<br />
| Usama<br />
|<br />
| <br />
|-style="background:beige"<br />
| [FEATURE] Enhance performance: performance for simple query<br />
| 2018/11/20<br />
|<br />
|<br />
| XLarge<br />
| Usama<br />
|<br />
| <br />
|-style="background:orange"<br />
| [FEATURE] Enhance performance: performance for extended query <br />
| 2019/01/17<br />
|<br />
|<br />
| <br />
| Ishii<br />
| <br />
| (1) Enhance performance for COPY XXX TO STDOUT (both for simple and extended query): [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=702f7c86f9b8f82f61e47235505715891ffe1b23 commit] <br> <br />
(2) Enhance performance for extended query message: <br> [https://www.pgpool.net/pipermail/pgpool-hackers/2019-February/003230.html [pgpool-hackers: 3230]] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=778f611e201d6df88ed90d01e49af77daf9f2926 commit] <br> (3) Eliminate select(2) calls in certain cases to enhance performance in simple and extended query: <br> [https://www.pgpool.net/pipermail/pgpool-hackers/2019-February/003247.html [pgpool-hackers: 3247]] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=cf5fe7eb89a11e3ada3833343c7ed6551ce7c662 commit]<br />
|-style="background:orange"<br />
| rowspan="2" | 009<br />
| [Documentation] Review and improve the current document<br />
| 2018/11/20<br />
| <br />
| High<br />
| Extra Large<br />
| Hoshiai<br />
|<br />
| [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=ea1998b7350de6882bea25fc3634c4f7673adbde commit1][https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=5f259f3b5e1b56763677d0b7aa736eb8772a8968 commit2][https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=b69e94e97ed4226e335e85f01bfc373c8e11db8f commit3] <br><br />
[https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=b69e94e97ed4226e335e85f01bfc373c8e11db8f commit4] <br />
[https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=c013bad08e67bd53d39a66835c67bc93d334d72b commit5]<br />
[https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=6d3939dac4d76eed5dcd1867fb16e8bc8215dc61 commit6]<br />
|-style="background:orange"<br />
| [Documentation] Update the examples to latest version.<br />
| 2018/11/20<br />
| <br />
| High<br />
| <br />
| Peng<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=0c9f716714dce156fe74469a933046b39896a072 commit] [http://www.pgpool.net/docs/latest/en/html/example-cluster.html doc] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=69c6a4cd5f49384a1d719e4e784ff84855f00a9d commit]<br />
|-style="background:beige"<br />
| 010<br />
| [FEATURE] Master watchdog sets quarantine state to primary node<br />
| 2018/11/26<br />
| <br />
| Normal<br />
| Small <br />
| Usama<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-March/002756.html [pgpool-hackers: 2756]] <br>[https://www.pgpool.net/pipermail/pgpool-general-jp/2018-March/001503.html [pgpool-general-jp: 1504]]<br />
| <br />
|-style="background:orange"<br />
| 011<br />
| [FEATURE] limiting number of frontends differently<br />
| 2018/11/26<br />
| 2018/12/04<br />
| <br />
| <br />
| Ishii<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-November/003153.html [pgpool-hackers: 3153]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=693a6284cf2dfc2e60d5a2489c9ee5167defc3dc commit]<br />
|-style="background:orange"<br />
| 012 <br />
| [FEATURE] Don't load balance after a SELECT having functions specified in black function list<br />
| 2018/11/29<br />
| 2019/06/30<br />
| Normal<br />
| Small<br />
| Peng<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2018-November/003157.html [pgpool-hackers: 3157]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=3ddf9aa0b20480b22bb5e8fc6097f2eb7cb56994 commit]<br />
|-style="background:orange"<br />
| 014<br />
| [FEATURE] Support for PostgreSQL 12.<br />
| 2018/11/29<br />
| <br />
| High<br />
| Small<br />
| Ishii<br />
| recovery.conf <br> pgpool_setup <br> pgppol-recovery extension<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=fda13a93a1025b498bb2a674fb49406d9e3e509c pgpool-recovery extension] <br> [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=23fb4c1250f0464a867f2ac69006d74f134213e3 pgpool_setup]<br />
|-style="background:orange"<br />
| 015<br />
| [FEATURE] Import PostgreSQL 12 parser.<br />
| 2018/11/29<br />
| 2019/07/31<br />
| High<br />
| Medium<br />
| Peng<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f694283cfd55a52750ce56697af2e5cd1d1da571 commit]<br />
|-style="background:orange"<br />
| 016<br />
| [FEATURE] Statement level load balancing<br />
| 2018/12/06<br />
| 2019/03/31<br />
| High<br />
| Large<br />
| Peng<br />
|<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=1099ba610eef06a9dab6f89486cc52de55ff3ebb commit]<br />
|-style="background:orange"<br />
| 018<br />
| [FEATURE] Add new columns to "show pool_nodes" command<br />
| 2019/04/22<br />
| 2019/04/24<br />
| High<br />
| Medium<br />
| Ishii<br />
| Discussion: [https://www.pgpool.net/pipermail/pgpool-hackers/2019-April/003315.html [pgpool-hackers: 3315]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=35cb1dc2d9d9f4887bd0407f150558660b7826e1 Commit]<br />
|-style="background:orange"<br />
| 019<br />
| [FEATURE][Document] Add new performance section<br />
| <br />
|<br />
| High<br />
| Medium<br />
| Ishii<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=854659a17b958536e80c461d55c9ba0f1032a128 commit]<br />
|-style="background:orange"<br />
| 020<br />
| [FEATURE] auto failback<br />
| 2019/5/23<br />
| 2019/7/5<br />
| <br />
| Medium<br />
| Hoshiai<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-May/003328.html [pgpool-hackers: 3328]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=3e2ecc970864056ff054799cac57ad5b30312c48 commit] <br />
|-style="background:orange"<br />
| 021<br />
| [FEATURE] allow to use md5 password in health_check_password and sr_check_password<br />
| 2019/5/30<br />
| 2019/6/10<br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-May/003334.html [pgpool-hackers: 3334]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=dc9742678dd04719a08a747d40cd4c0781fce49a commit]<br />
|-style="background:orange"<br />
| 022<br />
| [FEATURE] Routing relcache queries to load balance node<br />
| <br />
| <br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-June/003342.html [pgpool-hackers: 3342]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=46986ebc0be77e4b011b94b097789fec9e3f5b0f commit]<br />
|-style="background:orange"<br />
| 023<br />
| [FEATURE] Support ECDH key exchange with SSL<br />
| <br />
| <br />
| <br />
| Medium<br />
| Hoshiai<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=51bc494aaa7fd191e14038204d18effe2efb0ec8 commit1] [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f63c260d7e389bc03822721a9d66a0d6c7d22f4b commit2]<br />
|-style="background:orange"<br />
| 024<br />
| [FEATURE] Reduce relcahe queries<br />
| <br />
| <br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-June/003344.html [pgpool-hackers: 3344]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=6282805d4ae3f7a76ed607c0124420b8fe4c8320 commit]<br />
|-style="background:orange"<br />
| 025<br />
| [FEATURE] Eliminate temp table relcahe query<br />
| <br />
| <br />
| <br />
| Medium<br />
| Ishii<br />
| [https://www.pgpool.net/pipermail/pgpool-hackers/2019-June/003346.html [pgpool-hackers: 3346]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=7a0471bbcc3ab06a9cab9902d91e5c4c692b3284 commit]<br />
|-style="background:orange"<br />
| 026<br />
| [FEATURE] Add new arguments in pgpool_recovery function and failover_command/failback_command/follow_master_command.<br />
| <br />
| <br />
| <br />
| Small<br />
| Peng<br />
| <br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=ed90a39db3664eb7be85f192f5472cc0b59a2d8f commit]<br />
|-style="background:silver"<br />
| 101<br />
| 0000433: IN (SELECT ...) can not be rewritten in native replication mode<br />
| 2018/10/19<br />
| <br />
| <br />
| <br />
| Peng<br />
| [http://www.pgpool.net/mantisbt/view.php?id=433 bug433]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=d53292592a9808b260171f8569752ca89d7412fc commit] <br>Regression test should be added.<br />
|-style="background:silver"<br />
| 102<br />
| 0000434: Segmentation fault due to a query error and Sync messages in native replication mode<br />
| 2018/10/19<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| [https://www.pgpool.net/mantisbt/view.php?id=434 bug434]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=5e6d598b964ac88f41a18280f6289ca5e78ffad5 commit]<br />
|-style="background:silver"<br />
| 103<br />
| pool_passwd is corrupted.<br />
| 2018/10/22<br />
| <br />
| <br />
| <br />
| Hoshiai, Usama<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-October/003081.html [pgpool-hackers: 3081]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=d48cc28a7b2ac42185b48873608ff876f9298d89 commit]<br />
|-style="background:silver"<br />
| 104<br />
| [pgpool-hackers: 3025] Compile warns<br />
| 2018/10/22<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| [http://www.sraoss.jp/pipermail/pgpool-hackers/2018-August/003025.html [pgpool-hackers: 3025]]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bc9119f61b187577d64b63ebffb6f5412202f24f commit]<br />
|-style="background:silver"<br />
| 105<br />
| 0000443: Segmentation fault occurs when a certain Bind message is sent in native replication mode.<br />
| 2018/11/08<br />
| <br />
| <br />
| <br />
| Peng<br />
| [https://www.pgpool.net/mantisbt/view.php?id=443 bug443]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=1d8d03237a2ad507f8f1fb8fb0c84b3084f57cdc commit]<br />
|-style="background:silver"<br />
| 106<br />
| 0000444: pgpool does not take into account parameters order in startup packet<br />
| 2018/11/13<br />
| <br />
| <br />
| <br />
| Hoshiai<br />
| [https://www.pgpool.net/mantisbt/view.php?id=444 bug444]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=ffb998517bb91c512b77fbe1ca8ee331e492f131 commit]<br />
|-style="background:silver"<br />
| 107<br />
| 0000448: pgpool holds the connections as idle_in_transaction which are timed out due to idle_in_transaction setting on backend nodes<br />
| 2018/11/29<br />
| <br />
| <br />
| <br />
| Ishii<br />
| [https://www.pgpool.net/mantisbt/view.php?id=448 bug448]<br />
| Done. [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=3f5986eee360f12e6a0bb77aa46f95abf5f6bc10 commit]<br />
|-style="background:silver"<br />
| 108<br />
| [pgpool-general: 6351] kind mismatch among backends, savepoint with psqlodbc<br />
| 2018/12/26<br />
| <br />
| <br />
| <br />
| Peng<br />
| [https://www.pgpool.net/pipermail/pgpool-general/2018-December/006409.html [pgpool-general: 6351]]<br />
| <br />
|-style="background:silver"<br />
| 109<br />
| 0000455: watchdog lifecheck process has segfalut in query mode<br />
| 2019/01/21<br />
| <br />
| <br />
| <br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=455<br />
| Done. https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=4cde5da1b416d909d102cfe6878c0cd5189caf86<br />
|-style="background:white"<br />
| 110<br />
| Add regression test for query mode <br />
| 2019/01/21<br />
| <br />
| <br />
| <br />
| Peng<br />
| <br />
| <br />
|-style="background:white"<br />
| 111<br />
| 0000483: online-recovery is blocked after a child process exits abnormally with replication mode and watchdog<br />
| 2019/04/04 <br />
| <br />
| <br />
| <br />
| Usama<br />
| [https://www.pgpool.net/mantisbt/view.php?id=483 bug483]<br />
| Done [https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=c402060814ba9737e9572ba07eef1be7664c9679 commit].<br />
|-style="background:silver"<br />
| 112<br />
| Fix memory leak related to watchdog and auth pointed out by coverity<br />
| 2019/05/22<br />
| <br />
| <br />
|<br />
| Usama<br />
| src/auth/pool_hba.c src/auth/pool_auth.c src/auth/auth-scram.c src/watchdog/watchdog.c src/watchdog/wd_lifecheck.c src/config/pool_config_variable.c<br />
| <br />
|-style="background:white"<br />
| 113<br />
| Fix memory leak related to watchdog and auth pointed out by coverity<br />
| 2019/05/22<br />
| <br />
| <br />
| <br />
| ishii<br />
| other than :src/auth/pool_hba.c src/auth/pool_auth.c src/auth/auth-scram.c src/watchdog/watchdog.c src/watchdog/wd_lifecheck.c src/config/pool_config_variable.c<br />
| <br />
|-style="background:white"<br />
| 201<br />
| Feature Agreement <br />
| <br />
| <br />
| <br />
| <br />
|<br />
|<br />
| <br />
|-style="background:white"<br />
| 202<br />
| Feature Freeze <br />
| <br />
| 2019/08/15<br />
| <br />
| <br />
|<br />
|<br />
| <br />
|-style="background:white"<br />
| 203<br />
| Code Freeze <br />
| <br />
| 2019/08/31<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|<br />
|-style="background:white"<br />
| 204<br />
| Release beta1<br />
| <br />
| 2019/09/06<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|<br />
|-style="background:white"<br />
| 205<br />
| Official Release<br />
| <br />
| 2019/10/04<br />
| <br />
| <br />
|<br />
|<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=Pgpool-II_4.0_development&diff=2606
Pgpool-II 4.0 development
2018-06-22T07:01:16Z
<p>Usama: </p>
<hr />
<div>Last update: 2018/06/22 (gray items are done, yellow items are behind schedule, orange items are new features for 4.0, and pink items are other TODO)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]->postpone to 3.8<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]->postpone to 3.8<br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/4/6<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]->postpone to 3.8<br />
|-style="background:orange"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| 2018/4/18<br />
| Tatsuo<br />
| http://www.sraoss.jp/pipermail/pgpool-hackers/2018-March/002759.html http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| Completed.<br />
|-style="background:orange"<br />
| 62<br />
| [Feature] New feature candidate: SCRAM authentication and certification base authentication<br />
| 2017/3/23<br />
| 2018/6/28<br />(Ready for review)<br />
| Usama<br />
|<br />
| 2018/4/17: Ready for review(Include small Readme for testing). <br /> 2018/4/24: Documentation done. <br />2018/4/27: Regression done.<br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
| Ahsan<br />
| Similar to Oracle's "Transparent Application Failover".<br />
| Ahsan will post a proposal to pgpool-hackers<br />
|-style="background:orange"<br />
| 72<br />
| New feature candidate: Support more prefix for query routing (similar to NO LOAD BALANCE)<br />
| 2017/4/17<br />
| <br />
| Usama<br />
|<br />
| Postpone to 3.8<br />
|-style="background:white"<br />
| 83<br />
| [pgpool-hackers: 2400] Garbage output<br />
| 2017/6/19<br />
| <br />
|Usama<br />
|<br />
| Follow up: [pgpool-hackers: 2798]<br />
|-style="background:yellow"<br />
| 92<br />
| 0000322: PGPool child processes go into <defunct> state when a backend node is unresponsive<br />
| 2017/7/21<br />
|<br />
| Tatsuo<br />
|https://www.pgpool.net/mantisbt/view.php?id=322<br />
| Waiting for feedback (2018/3/22)<br />
|-style="background:yellow"<br />
| 104<br />
| 0000329: Newly elected(promoted) Pgpool does connect to any backend<br />
| 2017/8/11<br />
| 2017/12/11<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=329<br />
| fix in 3.7 done. Needs back patching<br />
|-style="background:silver"<br />
| 106<br />
| 0000332: Watch dog issue<br />
| 2017/8/24<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=332<br />
| Closed.(2018/1/9) Doesn't seems like an issue. Replied on Mantis.<br />
|-style="background:silver"<br />
| 111<br />
| 0000339: Failover does not occurr if master Pgpool-II and primary PostgreSQL servers are stopped at the same time<br />
| 2017/9/13<br />
| <br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=339<br />
| Closed. (2017/12/15) (Done in 3.6, 3.5, 3.7. Working on 3.4 and 3.3 --> Impossible due to technical reasons. Mantis updated). The report claimed that the bug was not fixed in 3.6.7. So reopen this item.<br />
|-style="background:silver"<br />
| 120<br />
| 0000349: Connection to PGpool Port through VIP fails to connect with JDBC, works fine with ODBC<br />
| 2017/10/5<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=349<br />
| Waiting for feedback.(2017/10/6)-->asking to close the issue (2017/12/8)-->They said they are going to upgrade on 2018/15 but no reply as of 2018/1/12 and waiting for feedback. The reporter said it will take more time because the organization is large (2018/2/28). Still no response. Polling again (2018/04/06). Still no response. Will close this issue on beginning of May.<br />
|-style="background:silver"<br />
| 123<br />
| [pgpoolAdmin] 0000361: Can't detach node from pgpoolAdmin UI, while pcp_detach_node works fine<br />
| 2017/11/01<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=361<br />
| Done. 2017/11/24<br />
|-style="background:white"<br />
| 125<br />
| 0000348: pgpool failover scenario ERROR - pgpool 3.6.6 (postgres 9.3.5)<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=348<br />
| Waiting for reply with message: Please try 3.6.7<br />
|-style="background:white"<br />
| 126<br />
| 0000342: On master fail slave not able to convert itself to master<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=342<br />
| Waiting for reply with message: Please try 3.6.7<br />
|-style="background:silver"<br />
| 127<br />
| [pgpoolAdmin]0000364: PGPool hangs when then number of connections are greater than num_init_children<br />
| 2017/11/10<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=364<br />
| Close(2018/04/02)<br />
|-style="background:silver"<br />
| 128<br />
| [pgpoolAdmin] 0000369: yum's baseurl does not exist and it can not be used<br />
| 2017/11/24<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=369<br />
| Done. (2017/11/27)<br />
|-style="background:silver"<br />
| 129<br />
| [pgpool-hackers: 2635] Some problems in Makefile.am<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002635.html<br />
| Done. 2018/1/8 https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=e9bbe227a3fbd92a947f87afd0aace7e0c5c4bec<br />
|-style="background:silver"<br />
| 130<br />
| $(top_srcdir) was created in src/parser/.<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| <br />
| Done. 2018/1/8 https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=e9bbe227a3fbd92a947f87afd0aace7e0c5c4bec<br />
|-style="background:pink"<br />
| 131<br />
| Logging client message<br />
| 2017/12/08<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002638.html<br />
| <br />
|-style="background:silver"<br />
| 132<br />
| 0000370: Pgpool get stuck with db exception followed by select<br />
| 2017/12/11<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=370<br />
| Close. (2018/3/5) Patch provided. Waiting for feedback.-> Resolved.<br />
|-style="background:silver"<br />
| 133<br />
| Failed in 002.native_replication. (Pgpool-II couldn't rewrite DEFAULT)<br />
| 2017/12/14<br />
| 2017/12/18<br />
| Peng<br />
| <br />
| Done.https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=b974f5f3b59b62ca3f0c5c0ccfdea125abbbc19b<br />
|-style="background:silver"<br />
| 134<br />
| [pgpoolAdmin] Pull Request<br />
| 2017/12/14<br />
|<br />
| Peng<br />
| https://github.com/pgpool/pgpooladmin/compare/master...remodoy:postgresql_connect_timeout<br />
| Done. https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=579833e695e011f8d47a6fff994a3393f9d8a37d<br />
|-style="background:silver"<br />
| 135<br />
| Modify pgpool.service to output log.<br />
| 2017/12/15<br />
| <br />
| Peng<br />
| <br />
| Done. 2017/12/21 <br> https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=63886312c702811f7ed53fac266c22946ba2212e<br />
|-style="background:orange"<br />
| 136<br />
| allow to specify load balance weight ratio for load balance parameters<br />
| 2017/12/15<br />
|<br />
| Peng<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002651.html<br />
| In progress.<br />
|-style="background:orange"<br />
| 137<br />
| Load-balancing control for specific queries<br />
| 2017/12/15<br />
| 2018/05/11<br />
| Peng<br />
|https://www.pgpool.net/pipermail/pgpool-hackers/2017-November/002594.html<br />
| Done. https://git.postgresql.org/gitweb/?p=pgpool2.git;a=search;s=Bo+Peng;st=author<br />
|-style="background:silver"<br />
| 138<br />
| Minor releases (3.7.1, 3.6.8 etc.)<br />
| 2017/12/15<br />
| 2018/1/9<br />
| Peng<br />
|<br />
| Done. 2018/1/9<br />
|-style="background:silver"<br />
| 139<br />
| 0000373: pgpool failed over<br />
| 2017/12/21<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=373<br />
| Waiting for feedback.-> no response. Closed.<br />
|-style="background:silver"<br />
| 140<br />
| 0000374: md5 authentication is broken<br />
| 2017/12/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=374<br />
| Waiting for feedback.-> no response. Closed.<br />
|-style="background:silver"<br />
| 141<br />
| 0000375: extended query error<br />
| 2018/01/08<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=375<br />
| Close.2018/4/27<br />
|-style="background:silver"<br />
| 142<br />
| 0000376: child process was terminated by segmentation fault<br />
| 2018/01/12<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=376<br />
| Closed. (2018/2/6)<br />
|-style="background:white"<br />
| 143<br />
| [pgpool-general: 5863] pgpool frequnet authentication timeout<br />
| 2018/01/19<br />
| <br />
| Usama<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2018-January/005921.html<br />
| In progress.<br />
|-style="background:silver"<br />
| 144<br />
| [pgpool-general: 5864] Troubleshooting assistance on node failure and connections blocking<br />
| 2018/01/19<br />
| <br />
| Tatsuo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2018-January/005922.html<br />
| Waiting for feedback (2017/1/19)-> No response from the poster over 1 month. Issue closed.<br />
|-style="background:white"<br />
| 145<br />
| [pgpool-general: 5899] Master Election - Priority<br />
| 2018/01/30<br />
| <br />
| Usama<br />
| https://www.pgpool.net/pipermail/pgpool-general/2018-January/005957.html<br />
|<br />
|-style="background:silver"<br />
| 146<br />
| 0000378: Pgpool fails all connections when secondary goes down<br />
| 2018/02/06<br />
| <br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=378<br />
| No response over 1 month. I am going to close the issue.<br />
|-style="background:silver"<br />
| 147<br />
| 0000379: Many connections go into state 'idle in transaction'<br />
| 2018/02/07<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=379<br />
| Patch provided. Waiting for feedback (2018/2/28)<br />
|-style="background:silver"<br />
| 148<br />
| 0000380: When a node is down, the first query to the cluster fails<br />
| 2018/02/14<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=380<br />
| It turned out a problem with user's setting.<br />
|-style="background:pink"<br />
| 149<br />
| Proposal: Enhancing pool_process and pool_pools<br />
| 2018/02/13<br />
|<br />
| Tatsuo<br />
| http://www.sraoss.jp/pipermail/pgpool-hackers/2018-February/002721.html<br />
| <br />
|-style="background:orange"<br />
| 150<br />
| Proposal: Disabling load balance after writing query<br />
| 2018/02/16<br />
| 2018/04/23<br />
| Tatsuo<br />
| http://www.sraoss.jp/pipermail/pgpool-hackers/2018-February/002726.html<br />
| Done (2018/4/23)<br />
|-style="background:silver"<br />
| 151<br />
| 0000385: arping, if_up_cmd' failed and failed to acquire delegate Ip<br />
| 2018/03/16<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=385<br />
| Close. (2018/3/26)<br />
|-style="background:silver"<br />
| 152<br />
| 0000386: Pgpool fails to start with a watchdog error<br />
| 2018/03/16<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=386<br />
| Close. (2018/04/27)<br />
|-style="background:silver"<br />
| 153<br />
| 0000388: pgpool-II 3.6.1 child process remain waiting for a non-existing client socket to send queries<br />
| 2018/03/18<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=388<br />
| Assigned (2018/04/06)-> Waiting for feedback (2018/05/07)->No feedback. Closed.<br />
|-style="background:white"<br />
| 154<br />
| 0000394: When multiple failover happens the pgpool pool node status is going into standby -stanby state<br />
| 2018/04/21<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=394<br />
| Assigned (2018/04/24)<br />
|-style="background:white"<br />
| 155<br />
| [pgpool-general: 6069] failover_require_consensus does not work.<br />
| 2018/05/03<br />
|<br />
| Usama<br />
| https://www.pgpool.net/pipermail/pgpool-general/2018-May/006127.html<br />
| Assigned (2018/05/07)<br />
|-style="background:white"<br />
| 156<br />
| [pgpool-hackers: 2807] client_min_messages<br />
| 2018/05/25<br />
|<br />
| Usama<br />
| http://www.sraoss.jp/pipermail/pgpool-hackers/2018-May/002807.html<br />
| Assigned (2018/05/25)<br />
|-style="background:orange"<br />
| 157<br />
| [Feature] Proposal: Add last state change timestamp to "show pool_nodes"<br />
| 2018/06/11<br />
|<br />
| Ishii<br />
| http://www.sraoss.jp/pipermail/pgpool-hackers/2018-June/002822.html<br />
| Done. (2018/06/12)<br />
|-style="background:white"<br />
| 158<br />
| 0000403: About : 0000402: write on backend 0 failed with error :"Success"<br />
| 2018/06/15<br />
|<br />
| Ishii<br />
| https://www.pgpool.net/mantisbt/view.php?id=403<br />
| Assigned.(2018/6/15) ->Waiting for feedback (2018/6/15)<br />
|-style="background:orange"<br />
| 159<br />
| [Feature] Add "last status change" to pcp_node_info and pgpool_adm like "show pool_nodes".<br />
| 2018/06/15<br />
|<br />
| Peng<br />
| <br />
| <br />
|-style="background:orange"<br />
| 160<br />
| [Feature] Add pid info to pcp_proc_info output.<br />
| 2018/06/15<br />
|<br />
|<br />
| <br />
|<br />
|-style="background:white"<br />
| 161<br />
| 0000405: ERROR: unable to read message length DETAIL: message length (8) in slot 1 does not match with slot 0(12) bash-4.1$<br />
| 2018/06/22<br />
|<br />
| <br />
| https://www.pgpool.net/mantisbt/view.php?id=405<br />
| Waiting for feedback. <br />
|-style="background:white"<br />
| 162<br />
| 0000406: failover called with old-primary = -1<br />
| 2018/06/22<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=406<br />
| Assigned<br />
|-style="background:white"<br />
| 163<br />
| 0000407: health check process doesn't start in some cases<br />
| 2018/06/22<br />
|<br />
| Ishii<br />
| https://www.pgpool.net/mantisbt/view.php?id=407<br />
| Waiting for feedback.<br />
|-style="background:white"<br />
| 164<br />
| [pgpool-general: 6134] kind mismatch among backends with multiple clients and prepared statements<br />
| 2018/06/22<br />
|<br />
| Ishii<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2018-June/006192.html<br />
| Assigned.<br />
|-style="background:white"<br />
| 200<br />
| Feature Agreement<br />
| <br />
| 2018/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 201<br />
| Feature Freeze<br />
| <br />
| 2018/8/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 202<br />
| Code Freeze<br />
| <br />
| 2018/9/30<br />
| <br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=Pgpool-II_4.0_development&diff=2431
Pgpool-II 4.0 development
2017-12-14T14:19:13Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/12/14 (gray items are done, yellow items are behind schedule, pink items are new features for 3.8)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]->postpone to 3.8<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]->postpone to 3.8<br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]->postpone to 3.8<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]->postpone to 3.8<br />
|-style="background:pink"<br />
| 62<br />
| [Feature] New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| Usama will post a proposal to pgpool-hackers<br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
| Ahsan will post a proposal to pgpool-hackers<br />
|-style="background:pink"<br />
| 72<br />
| New feature candidate: Support more prefix for query routing (similar to NO LOAD BALANCE)<br />
| 2017/4/17<br />
| <br />
| Usama<br />
|<br />
| Postpone to 3.8<br />
|-style="background:white"<br />
| 83<br />
| [pgpool-hackers: 2400] Garbage output<br />
| 2017/6/19<br />
| <br />
|Usama<br />
|<br />
|-style="background:yellow"<br />
| 92<br />
| 0000322: PGPool child processes go into <defunct> state when a backend node is unresponsive<br />
| 2017/7/21<br />
|<br />
| Tatsuo<br />
|https://www.pgpool.net/mantisbt/view.php?id=322<br />
| Seen similar issue when searching primary node is retrying<br />
|-style="background:yellow"<br />
| 104<br />
| 0000329: Newly elected(promoted) Pgpool does connect to any backend<br />
| 2017/8/11<br />
| 2017/12/11<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=329<br />
| fix in 3.7 done. Needs back patching<br />
|-style="background:yellow"<br />
| 106<br />
| 0000332: Watch dog issue<br />
| 2017/8/24<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=332<br />
| Doesn't seems like an issue. Replied on Mantis.<br />
|-style="background:yellow"<br />
| 111<br />
| 0000339: Failover does not occurr if master Pgpool-II and primary PostgreSQL servers are stopped at the same time<br />
| 2017/9/13<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=339<br />
| Done in 3.6, 3.5, 3.7. Working on 3.4 and 3.3 --> Impossible due to technical reasons. Mantis updated,<br />
|-style="background:white"<br />
| 120<br />
| 0000349: Connection to PGpool Port through VIP fails to connect with JDBC, works fine with ODBC<br />
| 2017/10/5<br />
|<br />
| ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=349<br />
| Waiting for feedback.(2017/10/6)-->asking to close the issue (2017/12/8)<br />
|-style="background:silver"<br />
| 123<br />
| [pgpoolAdmin] 0000361: Can't detach node from pgpoolAdmin UI, while pcp_detach_node works fine<br />
| 2017/11/01<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=361<br />
| Done. 2017/11/24<br />
|-style="background:white"<br />
| 125<br />
| 0000348: pgpool failover scenario ERROR - pgpool 3.6.6 (postgres 9.3.5)<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=348<br />
| Waiting for reply with message: Please try 3.6.7<br />
|-style="background:white"<br />
| 126<br />
| 0000342: On master fail slave not able to convert itself to master<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=342<br />
| Waiting for reply with message: Please try 3.6.7<br />
|-style="background:white"<br />
| 127<br />
| [pgpoolAdmin]0000364: PGPool hangs when then number of connections are greater than num_init_children<br />
| 2017/11/10<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=364<br />
| Waiting for feedback. (Requesting log file)<br />
|-style="background:silver"<br />
| 128<br />
| [pgpoolAdmin] 0000369: yum's baseurl does not exist and it can not be used<br />
| 2017/11/24<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=369<br />
| Done. (2017/11/27)<br />
|-style="background:white"<br />
| 129<br />
| [pgpool-hackers: 2635] Some problems in Makefile.am<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002635.html<br />
| Assigned.<br />
|-style="background:white"<br />
| 130<br />
| $(top_srcdir) was created in src/parser/.<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| <br />
| Assigned.<br />
|-style="background:pink"<br />
| 131<br />
| Logging client message<br />
| 2017/12/08<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002638.html<br />
| <br />
|-style="background:white"<br />
| 132<br />
| 0000370: Pgpool get stuck with db exception followed by select<br />
| 2017/12/11<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=370<br />
| Patch provided. Waiting for feedback.<br />
|-style="background:white"<br />
| 133<br />
| Failed in 002.native_replication. (Pgpool-II couldn't rewrite DEFAULT)<br />
| 2017/12/14<br />
|<br />
| Peng<br />
| <br />
| In progress.<br />
|-style="background:white"<br />
| 134<br />
| [pgpoolAdmin] Pull Request<br />
| 2017/12/14<br />
| https://github.com/pgpool/pgpooladmin/compare/master...remodoy:postgresql_connect_timeout<br />
| Peng<br />
| <br />
| Assigned<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=Pgpool-II_4.0_development&diff=2430
Pgpool-II 4.0 development
2017-12-14T14:16:05Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/12/14 (gray items are done, yellow items are behind schedule, pink items are new features for 3.8)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]->postpone to 3.8<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]->postpone to 3.8<br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]->postpone to 3.8<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]->postpone to 3.8<br />
|-style="background:pink"<br />
| 62<br />
| [Feature] New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| Usama will post a proposal to pgpool-hackers<br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
| Ahsan will post a proposal to pgpool-hackers<br />
|-style="background:pink"<br />
| 72<br />
| New feature candidate: Support more prefix for query routing (similar to NO LOAD BALANCE)<br />
| 2017/4/17<br />
| <br />
| Usama<br />
|<br />
| Postpone to 3.8<br />
|-style="background:white"<br />
| 83<br />
| [pgpool-hackers: 2400] Garbage output<br />
| 2017/6/19<br />
| <br />
|Usama<br />
|<br />
|-style="background:yellow"<br />
| 92<br />
| 0000322: PGPool child processes go into <defunct> state when a backend node is unresponsive<br />
| 2017/7/21<br />
|<br />
| Tatsuo<br />
|https://www.pgpool.net/mantisbt/view.php?id=322<br />
| Seen similar issue when searching primary node is retrying<br />
|-style="background:yellow"<br />
| 104<br />
| 0000329: Newly elected(promoted) Pgpool does connect to any backend<br />
| 2017/8/11<br />
| 2017/12/11<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=329<br />
| fix in 3.7 done. Needs back patching<br />
|-style="background:yellow"<br />
| 106<br />
| 0000332: Watch dog issue<br />
| 2017/8/24<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=332<br />
| Doesn't seems like an issue. Replied on Mantis.<br />
|-style="background:yellow"<br />
| 111<br />
| 0000339: Failover does not occurr if master Pgpool-II and primary PostgreSQL servers are stopped at the same time<br />
| 2017/9/13<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=339<br />
| Done in 3.6, 3.5, 3.7. Working on 3.4 and 3.3 --> Impossible due to technical reasons. Mantis updated,<br />
|-style="background:white"<br />
| 120<br />
| 0000349: Connection to PGpool Port through VIP fails to connect with JDBC, works fine with ODBC<br />
| 2017/10/5<br />
|<br />
| ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=349<br />
| Waiting for feedback.(2017/10/6)-->asking to close the issue (2017/12/8)<br />
|-style="background:silver"<br />
| 123<br />
| [pgpoolAdmin] 0000361: Can't detach node from pgpoolAdmin UI, while pcp_detach_node works fine<br />
| 2017/11/01<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=361<br />
| Done. 2017/11/24<br />
|-style="background:white"<br />
| 125<br />
| 0000348: pgpool failover scenario ERROR - pgpool 3.6.6 (postgres 9.3.5)<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=348<br />
| In progress<br />
|-style="background:white"<br />
| 126<br />
| 0000342: On master fail slave not able to convert itself to master<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=342<br />
| In progress<br />
|-style="background:white"<br />
| 127<br />
| [pgpoolAdmin]0000364: PGPool hangs when then number of connections are greater than num_init_children<br />
| 2017/11/10<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=364<br />
| Waiting for feedback. (Requesting log file)<br />
|-style="background:silver"<br />
| 128<br />
| [pgpoolAdmin] 0000369: yum's baseurl does not exist and it can not be used<br />
| 2017/11/24<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=369<br />
| Done. (2017/11/27)<br />
|-style="background:white"<br />
| 129<br />
| [pgpool-hackers: 2635] Some problems in Makefile.am<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002635.html<br />
| Assigned.<br />
|-style="background:white"<br />
| 130<br />
| $(top_srcdir) was created in src/parser/.<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| <br />
| Assigned.<br />
|-style="background:pink"<br />
| 131<br />
| Logging client message<br />
| 2017/12/08<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002638.html<br />
| <br />
|-style="background:white"<br />
| 132<br />
| 0000370: Pgpool get stuck with db exception followed by select<br />
| 2017/12/11<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=370<br />
| Patch provided. Waiting for feedback.<br />
|-style="background:white"<br />
| 133<br />
| Failed in 002.native_replication. (Pgpool-II couldn't rewrite DEFAULT)<br />
| 2017/12/14<br />
|<br />
| Peng<br />
| <br />
| In progress.<br />
|-style="background:white"<br />
| 134<br />
| [pgpoolAdmin] Pull Request<br />
| 2017/12/14<br />
| https://github.com/pgpool/pgpooladmin/compare/master...remodoy:postgresql_connect_timeout<br />
| Peng<br />
| <br />
| Assigned<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=Pgpool-II_4.0_development&diff=2429
Pgpool-II 4.0 development
2017-12-14T14:14:34Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/12/14 (gray items are done, yellow items are behind schedule, pink items are new features for 3.8)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]->postpone to 3.8<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]->postpone to 3.8<br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]->postpone to 3.8<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]->postpone to 3.8<br />
|-style="background:pink"<br />
| 62<br />
| [Feature] New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| Usama will post a proposal to pgpool-hackers<br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
| Ahsan will post a proposal to pgpool-hackers<br />
|-style="background:pink"<br />
| 72<br />
| New feature candidate: Support more prefix for query routing (similar to NO LOAD BALANCE)<br />
| 2017/4/17<br />
| <br />
| Usama<br />
|<br />
| Postpone to 3.8<br />
|-style="background:white"<br />
| 83<br />
| [pgpool-hackers: 2400] Garbage output<br />
| 2017/6/19<br />
| <br />
|Usama<br />
|<br />
|-style="background:yellow"<br />
| 92<br />
| 0000322: PGPool child processes go into <defunct> state when a backend node is unresponsive<br />
| 2017/7/21<br />
|<br />
| Tatsuo<br />
|https://www.pgpool.net/mantisbt/view.php?id=322<br />
| Seen similar issue when searching primary node is retrying<br />
|-style="background:yellow"<br />
| 104<br />
| 0000329: Newly elected(promoted) Pgpool does connect to any backend<br />
| 2017/8/11<br />
| 2017/12/11<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=329<br />
| fix in 3.7 done. Needs back patching<br />
|-style="background:yellow"<br />
| 106<br />
| 0000332: Watch dog issue<br />
| 2017/8/24<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=332<br />
| Doesn't seems like an issue. Replied on Mantis.<br />
|-style="background:yellow"<br />
| 111<br />
| 0000339: Failover does not occurr if master Pgpool-II and primary PostgreSQL servers are stopped at the same time<br />
| 2017/9/13<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=339<br />
| Done in 3.6, 3.5, 3.7. Working on 3.4 and 3.3 --> Impossible due to technical reasons. Usama will comment on Mantis,<br />
|-style="background:white"<br />
| 120<br />
| 0000349: Connection to PGpool Port through VIP fails to connect with JDBC, works fine with ODBC<br />
| 2017/10/5<br />
|<br />
| ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=349<br />
| Waiting for feedback.(2017/10/6)-->asking to close the issue (2017/12/8)<br />
|-style="background:silver"<br />
| 123<br />
| [pgpoolAdmin] 0000361: Can't detach node from pgpoolAdmin UI, while pcp_detach_node works fine<br />
| 2017/11/01<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=361<br />
| Done. 2017/11/24<br />
|-style="background:white"<br />
| 125<br />
| 0000348: pgpool failover scenario ERROR - pgpool 3.6.6 (postgres 9.3.5)<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=348<br />
| In progress<br />
|-style="background:white"<br />
| 126<br />
| 0000342: On master fail slave not able to convert itself to master<br />
| 2017/11/09<br />
|<br />
| Usama<br />
| https://www.pgpool.net/mantisbt/view.php?id=342<br />
| In progress<br />
|-style="background:white"<br />
| 127<br />
| [pgpoolAdmin]0000364: PGPool hangs when then number of connections are greater than num_init_children<br />
| 2017/11/10<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=364<br />
| Waiting for feedback. (Requesting log file)<br />
|-style="background:silver"<br />
| 128<br />
| [pgpoolAdmin] 0000369: yum's baseurl does not exist and it can not be used<br />
| 2017/11/24<br />
|<br />
| Peng<br />
| https://www.pgpool.net/mantisbt/view.php?id=369<br />
| Done. (2017/11/27)<br />
|-style="background:white"<br />
| 129<br />
| [pgpool-hackers: 2635] Some problems in Makefile.am<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002635.html<br />
| Assigned.<br />
|-style="background:white"<br />
| 130<br />
| $(top_srcdir) was created in src/parser/.<br />
| 2017/12/08<br />
|<br />
| Peng<br />
| <br />
| Assigned.<br />
|-style="background:pink"<br />
| 131<br />
| Logging client message<br />
| 2017/12/08<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/pipermail/pgpool-hackers/2017-December/002638.html<br />
| <br />
|-style="background:white"<br />
| 132<br />
| 0000370: Pgpool get stuck with db exception followed by select<br />
| 2017/12/11<br />
|<br />
| Tatsuo<br />
| https://www.pgpool.net/mantisbt/view.php?id=370<br />
| Patch provided. Waiting for feedback.<br />
|-style="background:white"<br />
| 133<br />
| Failed in 002.native_replication. (Pgpool-II couldn't rewrite DEFAULT)<br />
| 2017/12/14<br />
|<br />
| Peng<br />
| <br />
| In progress.<br />
|-style="background:white"<br />
| 134<br />
| [pgpoolAdmin] Pull Request<br />
| 2017/12/14<br />
| https://github.com/pgpool/pgpooladmin/compare/master...remodoy:postgresql_connect_timeout<br />
| Peng<br />
| <br />
| Assigned<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=2010
pgpool-II 3.7 development
2017-04-17T13:59:02Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/04/14 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
| 2017/5/31<br />
| Ishii<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation] Proposal: http://www.pgpool.net/pipermail/pgpool-hackers/2017-March/002213.html<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-style="background:silver"<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)->Closed (2017/3/26).<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:silver"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Closed<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| waiting for feedback (2017/4/3)<br />
|-style="background:silver"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] closed on 2017/3/31<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/4/30<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/4/30<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:silver"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23->Closed on 3/26<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/4/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned (resolved)<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/4/05<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned (resolved)<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Fixed. https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commitdiff;h=4615f807179fbfbdb18c7856e109d95f53abc201<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| Fixed on 2017/3/24<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/4/14<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Waiting for feedback<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| Peng<br />
| <br />
| Depends of PostgreSQL RC release.<br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 65<br />
| PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog<br />
| 2017/3/23<br />
| 2017/4/14<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=293<br />
| Waiting for feedback. The bug is fixed in pgpoolAdmin 3.6.0.<br />
|-style="background:silver"<br />
| 66<br />
| pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156<br />
| 2017/3/24<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=298<br />
| Fixed. (.pcppass file is required.)<br />
|-style="background:white"<br />
| 67<br />
| Minor release<br />
| 2017/3/27<br />
| 2017/4/30<br />
| Peng<br />
| <br />
| Assigned<br />
|-style="background:silver"<br />
| 68<br />
| [pgpool-general: 5396] pam ldap failure<br />
| 2017/3/30<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-March/005454.html<br />
| Fixed on 2017/3/31<br />
|-style="background:white"<br />
| 69<br />
| New Defects reported by Coverity Scan for pgpool-II<br />
| 2017/4/4<br />
| <br />
| Usama<br />
| <br />
| <br />
|-style="background:silver"<br />
| 70<br />
| Errors on the reloading of configuration<br />
| 2017/4/7<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=299<br />
| Fixed on 2017/4/12<br />
|-style="background:white"<br />
| 71<br />
| 0000300: pgpool-II doesn't handle lost socket file<br />
| 2017/4/14<br />
| <br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=300<br />
|<br />
|-style="background:pink"<br />
| 72<br />
| New feature candidate: Support more prefix for query routing (similar to NO LOAD BALANCE)<br />
| 2017/4/17<br />
| <br />
| Usama<br />
|<br />
| <br />
|-style="background:silver"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=2007
pgpool-II 3.7 development
2017-04-13T14:26:22Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/04/07 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
| 2017/5/31<br />
| Ishii<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation] Proposal: http://www.pgpool.net/pipermail/pgpool-hackers/2017-March/002213.html<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-style="background:silver"<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)->Closed (2017/3/26).<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:silver"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Closed<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| waiting for feedback (2017/4/3)<br />
|-style="background:silver"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] closed on 2017/3/31<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/4/30<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/4/30<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:silver"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23->Closed on 3/26<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/4/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned (resolved)<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/4/05<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned (resolved)<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Fixed. https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commitdiff;h=4615f807179fbfbdb18c7856e109d95f53abc201<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| Fixed on 2017/3/24<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/4/14<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Waiting for feedback<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| Peng<br />
| <br />
| Depends of PostgreSQL RC release.<br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 65<br />
| PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog<br />
| 2017/3/23<br />
| 2017/4/14<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=293<br />
| Waiting for feedback. The bug is fixed in pgpoolAdmin 3.6.0.<br />
|-style="background:silver"<br />
| 66<br />
| pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156<br />
| 2017/3/24<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=298<br />
| Fixed. (.pcppass file is required.)<br />
|-style="background:white"<br />
| 67<br />
| Minor release<br />
| 2017/3/27<br />
| 2017/4/30<br />
| Peng<br />
| <br />
| Assigned<br />
|-style="background:silver"<br />
| 68<br />
| [pgpool-general: 5396] pam ldap failure<br />
| 2017/3/30<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-March/005454.html<br />
| Fixed on 2017/3/31<br />
|-style="background:white"<br />
| 69<br />
| New Defects reported by Coverity Scan for pgpool-II<br />
| 2017/4/4<br />
| <br />
| Usama<br />
| <br />
| <br />
|-style="background:silver"<br />
| 70<br />
| Errors on the reloading of configuration<br />
| 2017/4/7<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=299<br />
| Fixed on 2017/4/12<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=2006
pgpool-II 3.7 development
2017-04-12T14:52:12Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/04/07 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
| 2017/5/31<br />
| Ishii<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation] Proposal: http://www.pgpool.net/pipermail/pgpool-hackers/2017-March/002213.html<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-style="background:silver"<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)->Closed (2017/3/26).<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:silver"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Closed<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| waiting for feedback (2017/4/3)<br />
|-style="background:silver"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] closed on 2017/3/31<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/4/30<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/4/30<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:silver"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23->Closed on 3/26<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/4/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/4/05<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Fixed. https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commitdiff;h=4615f807179fbfbdb18c7856e109d95f53abc201<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| Fixed on 2017/3/24<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/4/14<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Waiting for feedback<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| Peng<br />
| <br />
| Depends of PostgreSQL RC release.<br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 65<br />
| PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog<br />
| 2017/3/23<br />
| 2017/4/14<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=293<br />
| Waiting for feedback. The bug is fixed in pgpoolAdmin 3.6.0.<br />
|-style="background:silver"<br />
| 66<br />
| pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156<br />
| 2017/3/24<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=298<br />
| Fixed. (.pcppass file is required.)<br />
|-style="background:white"<br />
| 67<br />
| Minor release<br />
| 2017/3/27<br />
| 2017/4/30<br />
| Peng<br />
| <br />
| Assigned<br />
|-style="background:silver"<br />
| 68<br />
| [pgpool-general: 5396] pam ldap failure<br />
| 2017/3/30<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-March/005454.html<br />
| Fixed on 2017/3/31<br />
|-style="background:white"<br />
| 69<br />
| New Defects reported by Coverity Scan for pgpool-II<br />
| 2017/4/4<br />
| <br />
| Usama<br />
| <br />
| <br />
|-style="background:silver"<br />
| 70<br />
| Errors on the reloading of configuration<br />
| 2017/4/7<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=299<br />
| Fixed on 2017/4/12<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1982
pgpool-II 3.7 development
2017-03-31T15:37:03Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/31 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Ishii<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation] Proposal: http://www.pgpool.net/pipermail/pgpool-hackers/2017-March/002213.html<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-style="background:silver"<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)->Closed (2017/3/26).<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] waiting for feedback<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:silver"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23->Closed on 3/26<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/4/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/4/05<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| Fixed on 2017/3/24<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| Peng<br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 65<br />
| PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog<br />
| 2017/3/23<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=293<br />
| Assigned<br />
|-style="background:white"<br />
| 66<br />
| pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156<br />
| 2017/3/24<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=298<br />
| Assigned<br />
|-style="background:white"<br />
| 67<br />
| RPMリリース<br />
| 2017/3/27<br />
| <br />
| Peng<br />
| <br />
| Assigned<br />
|-style="background:silver"<br />
| 68<br />
| [pgpool-general: 5396] pam ldap failure<br />
| 2017/3/30<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-March/005454.html<br />
| Fixed on 2017/3/31<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1978
pgpool-II 3.7 development
2017-03-30T16:29:22Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/30 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Ishii<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-style="background:silver"<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)->Closed (2017/3/26).<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] in progress<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:silver"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23->Closed on 3/26<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/4/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/4/05<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| Fixed on 2017/3/24<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| Peng<br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 65<br />
| PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog<br />
| 2017/3/23<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=293<br />
| Assigned<br />
|-style="background:white"<br />
| 66<br />
| pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156<br />
| 2017/3/24<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=298<br />
| Assigned<br />
|-style="background:white"<br />
| 67<br />
| RPMリリース<br />
| 2017/3/27<br />
| <br />
| Peng<br />
| <br />
| Assigned<br />
|-style="background:white"<br />
| 68<br />
| [pgpool-general: 5396] pam ldap failure<br />
| 2017/3/30<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-March/005454.html<br />
| Assigned<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1974
pgpool-II 3.7 development
2017-03-29T21:27:04Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/27 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Ishii<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-style="background:silver"<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)->Closed (2017/3/26).<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] in progress<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:silver"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23->Closed on 3/26<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| Fixed on 2017/3/24<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| Peng<br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 65<br />
| PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog<br />
| 2017/3/23<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=293<br />
| Assigned<br />
|-style="background:white"<br />
| 66<br />
| pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156<br />
| 2017/3/24<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=298<br />
| Assigned<br />
|-style="background:white"<br />
| 67<br />
| RPMリリース<br />
| 2017/3/27<br />
| <br />
| Peng<br />
| <br />
| Assigned<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1959
pgpool-II 3.7 development
2017-03-22T08:50:04Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/22 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/25<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] in progress<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] In porgress<br />
|-style="background:yellow"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23.<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| <br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1958
pgpool-II 3.7 development
2017-03-22T08:25:31Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/22 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] in progress<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] In porgress<br />
|-style="background:yellow"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23.<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| Depend on #46<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| <br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1957
pgpool-II 3.7 development
2017-03-22T08:24:02Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/22 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] in progress<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] In porgress<br />
|-style="background:yellow"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23.<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| <br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1956
pgpool-II 3.7 development
2017-03-22T08:21:55Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/22 (gray items are done, yellow items are behind schedule, pink items are new features for 3.7)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-style="background:pink"<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:pink"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-style="background:pink"<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-style="background:pink"<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-style="background:yellow"<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned->waiting for feedback (2017/3/12)<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] in progress<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] in progress<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:pink"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:pink"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] in progress<br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:yellow"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] In porgress<br />
|-style="background:yellow"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback from 3017/2/23. Will close on 3/23.<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| 2017/3/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 59<br />
| PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking'<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=296<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 60<br />
| Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427<br />
| 2017/3/21<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=297<br />
| [SL: 3] Assigned<br />
|-style="background:pink"<br />
| 61<br />
| New feature candidate: import PostgreSQL 10.0 SQL parser<br />
| 2017/3/23<br />
| <br />
| <br />
| <br />
| <br />
|-style="background:pink"<br />
| 62<br />
| New feature candidate: certification base authentication<br />
| 2017/3/23<br />
| <br />
| <br />
|<br />
| <br />
|-style="background:pink"<br />
| 63<br />
| New feature candidate: Seamless Application Failover<br />
| 2017/3/23<br />
| <br />
|<br />
| Similar to Oracle's "Transparent Application Failover".<br />
|<br />
|-style="background:silver"<br />
| 64<br />
| Pgpool-II minor releases (3.6.2, 3.5.6, 3.4.10, 3.3.14, 3.2.19)<br />
| 2017/3/17<br />
| 2017/3/17<br />
| Peng<br />
| <br />
|<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1921
pgpool-II 3.7 development
2017-03-15T07:28:46Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/03/15 (gray items are done, yellow items are behind schedule)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:white"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| [Feature: small]<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:silver"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-style="background:silver"<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:silver"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| Peng<br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:white"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] patch created and waiting for feedback.<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] Assigned<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:white"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| Tatsuo/Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| [Feature: Medium][medium size implementation]<br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation] waiting feedback from Usama<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] Assigned <br />
|-style="background:silver"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Done<br />
|-style="background:white"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] In porgress<br />
|-style="background:white"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback<br />
|-style="background:silver"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] Done<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:silver"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 57<br />
| [pgpool-general: 5350] pgpooladmin version issue<br />
| 2017/3/3<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005408.html<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 58<br />
| Pgpool service fails to start on the load of OS<br />
| 2017/3/15<br />
| 2017/3/31<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=294<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1909
pgpool-II 3.7 development
2017-03-01T15:29:18Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/02/28 (gray items are done, yellow items are behind schedule)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:white"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Low priority<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:yellow"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] [Feedback 2017/3/1]<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:yellow"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| <br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] patch created and waiting for feedback.<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] Assigned<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:white"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| <br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation]<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] Assigned <br />
|-style="background:white"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] (waiting for feedback)<br />
|-style="background:white"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:white"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] waiting for feedback (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1908
pgpool-II 3.7 development
2017-02-28T15:16:51Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/02/28 (gray items are done, yellow items are behind schedule)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:white"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Low priority<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:yellow"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] in progress<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|- style="background:silver"<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][closed 2017/2/28][unable to reproduce] [no response from user]<br />
|- style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:yellow"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| <br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] patch created and waiting for feedback.<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] Assigned<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:silver"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Fixed https://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=commit;h=ab3ece87c77cf2eeb09799465ec42285966be3d1<br />
|-style="background:silver"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:white"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| <br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation]<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| 2017/3/10<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] Assigned <br />
|-style="background:white"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] (waiting for feedback)<br />
|-style="background:white"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:white"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] waiting for feedback (code committed)<br />
|-style="background:white"<br />
| 55<br />
| Inconsistent backend state<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=289<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 56<br />
| [safety violation] master without quorum execute failover procedure<br />
| 2017/2/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=290<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1897
pgpool-II 3.7 development
2017-02-23T19:34:15Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/02/23 (gray items are done, yellow items are behind schedule)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:white"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Low priority<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:yellow"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] in progress<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|-<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2017/3/10<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][SL: 3] assigned<br />
|-style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| Resolved<br />
|-<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| 2017/3/07<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:yellow"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| <br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] patch created and waiting for feedback.<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] Assigned<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:yellow"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Assigned<br />
|-style="background:white"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:white"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| <br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation]<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] Assigned <br />
|-style="background:white"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] (waiting for feedback)<br />
|-style="background:white"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:white"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] waiting for feedback (code committed)<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1896
pgpool-II 3.7 development
2017-02-23T18:02:01Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/02/23 (gray items are done, yellow items are behind schedule)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| Usama<br />
| add new child if it goes down<br />
| [Feature: small]<br />
|- style="background:white"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Low priority<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
| Tatsuo<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| [Feature: small] [medium size implementation]<br />
|-<br />
|-<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
| Usama<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| [Feature: medium] [medium size implementation]<br />
|-style="background:silver"<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3] Closed.<br />
|-style="background:yellow"<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] in progress<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| 2017/2/28<br />
| Ahsan<br />
|<br />
| [SL : 3] assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3] Not reproduced here. Waiting for feedback.(2017/2/23)<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|-<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2016/9/20<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][SL: 3] assigned<br />
|-style="background:silver"<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-style="background:silver"<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] done (2017/2/8)<br />
|-style="background:silver"<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog (2017/2/8)<br />
|-<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] not reproduced<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-style="background:silver"<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| assigned<br />
|-<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] in progress<br />
|-style="background:silver"<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.](2017/2/8)<br />
|-style="background:yellow"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| <br />
| <br />
|<br />
|-style="background:silver"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] fix committed on 2017/1/12. Issue closed.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:yellow"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned<br />
|-style="background:silver"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:silver"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1] patch created and waiting for feedback.<br />
|-style="background:silver"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Fix committed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] Assigned<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:yellow"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| 2017/2/16<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Assigned<br />
|-style="background:white"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| 2017/2/28<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:silver"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2] not reproduced -> close (2017/2/8)<br />
|-style="background:silver"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Same issue as bug271 (item 35)<br />
|-style="background:white"<br />
| 43<br />
| new feature candidate: verify standby node while finding primary node<br />
| 2017/1/12<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001979.html<br />
| <br />
|-style="background:silver"<br />
| 44<br />
| [pgpool-general: 5223] Questionable Failover<br />
| 2017/1/12<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-January/005281.html<br />
| Done (2017/2/8)<br />
|-style="background:silver"<br />
| 45<br />
| stack smashing detected<br />
| 2017/1/18<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=280<br />
| Done (2017/2/8)<br />
|-style="background:white"<br />
| 46<br />
| new feature candidate: Proposal to make backend node failover mechanism quorum aware<br />
| 2017/1/10<br />
| <br />
| <br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2017-January/001974.html<br />
| [Feature: large][Medium size implementation]<br />
|-style="background:silver"<br />
| 47<br />
| "segmentation fault" when execute pcp_attach_node<br />
| 2017/1/27<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=281<br />
| [SL: 2] in progress<br />
|-style="background:white"<br />
| 48<br />
| PGPool hangs in Master/Slave mode with Slony submodule<br />
| 2017/2/8<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=283<br />
| [SL: 2] Assigned <br />
|-style="background:white"<br />
| 49<br />
| pgpool-II native replication loses sync every 1-2 days<br />
| 2017/2/8<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=284<br />
| [SL: 2] Assigned <br />
|-style="background:white"<br />
| 50<br />
| pgpool hangs with hibernate and spring<br />
| 2017/2/8<br />
| 2017/2/28<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=286<br />
| [SL: 2] waiting for feedback<br />
|-style="background:white"<br />
| 51<br />
| Syntax Error in Query Using CURRENT_TIMESTAMP<br />
| 2017/2/23<br />
| 2017/3/23<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=287<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 52<br />
| Pgpool hangs on query and doesn't send it to backend<br />
| 2017/2/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=282<br />
| [SL: 3] waiting for feedback<br />
|-style="background:white"<br />
| 53<br />
| FATAL: failed to read kind from backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=288<br />
| [SL: 3] Assigned<br />
|-style="background:white"<br />
| 54<br />
| [pgpool-general: 5315] pg_terminate_backend<br />
| 2017/2/23<br />
| <br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2017-February/005373.html<br />
| [SL: 3] waiting for feedback (code committed)<br />
|-style="background:white"<br />
| 100<br />
| Feature Agreement<br />
| <br />
| 2017/3/31<br />
| <br />
|<br />
| <br />
|-style="background:white"<br />
| 101<br />
| Feature Freeze <br />
| <br />
| 2017/8/31<br />
| <br />
|<br />
| <br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.7_development&diff=1846
pgpool-II 3.7 development
2017-01-10T10:56:10Z
<p>Usama: </p>
<hr />
<div>Last update: 2017/01/09 (gray items are done, yellow items are behind schedule)<br />
<br />
Each bug items assigned "SL (Severity level)" from 1-3 (1 is the most severe, 3 is the least severe) in "Status" column.<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|-style="background:silver"<br />
| 1<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6 -> the data taken was not using provisioned IO and the data is not very useful. Remove the item and expect another chance (PGECons?)<br />
|-<br />
| 2<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.7<br />
|- style="background:white"<br />
| 3<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Low priority<br />
|-style="background:silver"<br />
| 4<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| 2016/8/31<br />
| Usama<br />
|<br />
| <br />
|-<br />
| 5<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_multiple_pgpool-II_instances_with_in-memory_query_cache_enabled<br />
| Low priority<br />
|-<br />
|-<br />
| 6<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| Low priority<br />
|-<br />
| 7<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| [SL: 3]<br />
|-<br />
| 8<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| [SL: 3] in progress<br />
|-style="background:silver"<br />
| 9<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/8/15<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=39d24e7f7ff88dfa780982059421ff6f405e63db<br />
|-<br />
| 10<br />
| testing of new failover code<br />
| 2016/6/6<br />
| <br />
| Ahsan<br />
|<br />
| assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 11<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
| 2016/8/26<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| [SL: 3]<br />
|-style="background:silver"<br />
| 12<br />
| failover not performed by stanby node<br />
| 2016/8/2<br />
| 2016/10/7<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=227<br />
| [3.6 RC1] in progress<br />
|- style="background:silver"<br />
| 13<br />
| packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2']<br />
| 2016/8/15<br />
| 2016/9/30<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=231<br />
| <del>[3.6 beta]</del> In progress -> done (2016/12/20)<br />
|-<br />
| 14<br />
| [pgpool-general: 4912] Pgpool and IP bonding<br />
| 2016/8/18<br />
| 2016/9/20<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-general/2016-August/004970.html<br />
| [3.6 RC1][SL: 3] assigned<br />
|-<br />
| 15<br />
| watchdog can start even in case VIP is brought up in other nodes.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog<br />
|-<br />
| 16<br />
| watchdog can start even in case trusted servers are not reachable.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog<br />
|-<br />
| 17<br />
| watchdogs with different VIP can exist in a cluster.<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog<br />
|-<br />
| 18<br />
| Behavior when watchdog process is killed<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| [SL:1] assigned<br />
|-<br />
| 19<br />
| Changed behavior when all heartbeat LAN are disconnected<br />
| 2016/8/23<br />
| <br />
| Usama<br />
|<br />
| Not a bug: Expected behavior with new watchdog<br />
|-<br />
| 20<br />
| Connections remains open when backend dettach during a transaction<br />
| 2016/9/2<br />
| <br />
| Pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=240<br />
| [SL: 1] waiting for feedback (It wasn't reproduced)-->There was an already feedback on 10/3.<br />
|-style="background:silver"<br />
| 21<br />
| pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies<br />
| 2016/9/6<br />
| 2016/9/30<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=234<br />
| <del>[3.6 beta]</del>(same as #79)assigned <br />
|-<br />
| 22<br />
| [Pgpool:1815] Re: Fw: New Defects reported by Coverity Scan for pgpool-II (1)-(5)<br />
| 2016/9/9<br />
| 2016/9/30<br />
| Usama<br />
| <br />
| [3.6 RC1] assigned<br />
|-style="background:silver"<br />
| 23<br />
| watchdog sometimes fails de-escalation<br />
| 2016/9/21<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=249<br />
| assigned<br />
|-<br />
| 24<br />
| Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=250<br />
| [SL:2] assigned<br />
|-<br />
| 25<br />
| failover_command not executed<br />
| 2016/9/28<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=251<br />
| assigned [Need verification: Should already be fixed in the latest version.]<br />
|-style="background:yellow"<br />
| 26<br />
| pgpoolAdmin 3.6 release<br />
|<br />
| 2016/12/31<br />
| <br />
| <br />
|<br />
|-style="background:white"<br />
| 27<br />
| pgpool-II sometimes hangs on restart<br />
| 2016/12/06<br />
| <br />
| Ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=265<br />
| [SL: 2] waiting for feedback.<br />
|-style="background:silver"<br />
| 28<br />
| [pgpool-general: 5172] Version 3.6 is missing pgpool_adm extension<br />
| 2016/12/19<br />
| 2016/12/22<br />
| Peng<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-December/005230.html<br />
| Fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f8a157a1288c1ee452e981151b58875540a5cc90<br />
|-style="background:white"<br />
| 29<br />
| While attaching nodes in replication mode "show pool_nodes" is showing different values on each node<br />
| 2016/12/20<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=258<br />
| [SL:3] Assigned<br />
|-style="background:white"<br />
| 30<br />
| Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=266<br />
| [SL: 2] Assigned<br />
|-style="background:white"<br />
| 31<br />
| log_destination is set to syslog but pgpool does not use /dev/log<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=267<br />
| [SL: 2] Assigned<br />
|-style="background:white"<br />
| 32<br />
| pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off<br />
| 2016/12/20<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=268<br />
| Assigned [Fixed in latest version]<br />
|-style="background:silver"<br />
| 33<br />
| authentication timeout with connection_life_time<br />
| 2016/12/20<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=269<br />
| Assigned<br />
|-style="background:white"<br />
| 34<br />
| pgpool system hung cause parallel many query<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=270<br />
| Assigned<br />
|-style="background:white"<br />
| 35<br />
| balanced requests after started transaction<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=271<br />
| [SL: 1]<br />
|-style="background:white"<br />
| 36<br />
| pgpool not releasing shared memory segments<br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=272<br />
| [SL: 2] Patch proposed.<br />
|-style="background:white"<br />
| 37<br />
| ERROR: unable to read data from frontend<br />
| 2016/12/20<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=273<br />
| [SL:1] Assigned<br />
|-style="background:silver"<br />
| 38<br />
| PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? <br />
| 2016/12/20<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=274<br />
| Assigned<br />
|-style="background:white"<br />
| 39<br />
| superuser: unknown (Connection error) in pgpoolAdmin<br />
| 2017/01/06<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=276<br />
| [SL: 2] Assigned<br />
|-style="background:white"<br />
| 40<br />
| pgpoolAdmin is missing in yum repository pgpool36<br />
| 2017/01/06<br />
| <br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=277<br />
| [SL:2] Assigned<br />
|-style="background:white"<br />
| 41<br />
| Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)"<br />
| 2016/11/10<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=260<br />
| [SL: 2]<br />
|-style="background:white"<br />
| 42<br />
| Load balancing error<br />
| 2016/9/23<br />
| <br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=244<br />
| [SL: 2] Waiting for feedback<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1518
pgpool-II 3.6 development
2016-07-21T19:49:39Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/7/15 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-style="background:silver"<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| 2016/07/08<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6. Usama will review this until 12 June.　follow up by Usama in [pgpool-general: 4721] http://www.pgpool.net/pipermail/pgpool-general/2016-June/004779.html -- done on 2016/07/12<br />
|-style="background:silver"<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| 2016/5/13<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6, strongly connected to item 11.--> Not necessary any more.<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| 2016/07/25<br />
| Usama<br />
| deal with pg_terminate_backend<br />
| in progress need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| 2016/8/31<br />
| Peng<br />
| <br />
| [In progress] Will start after PostgreSQL 9.6 beta released<br />
|-style="background:silver"<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/5/19<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly. Done on 2016/5/21.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 9-4<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/27<br />
| 2016/8/31<br />
| Tatsuo, Peng, Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| [in progress] See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/<br />
|-<br />
| 9-5<br />
| Convert the pgpool documentation to SGML (Tatsuo)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Tatsuo<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| [in progress] See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Preface, Tutorial.Getting Started, Server Administration.pgpool-II Installation from Source Code, Server Administration.Server Setup and Operation<br />
|-<br />
| 9-6<br />
| Convert the pgpool documentation to SGML (Usama)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Tutorial.Watchdog, Server Administration.Server Configuration, Server Administration.Client Authentication, Examples<br />
|-<br />
| 9-7<br />
| Convert the pgpool documentation to SGML (Pengbo)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Pengbo<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Reference<br />
|- style="background:white"<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Lower　the priority<br />
|-style="background:silver"<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/5/13<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted. At this point pcp_detach_node does not break in certain cases (load balance node is not detached)<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| Will do after #8 and #8 are finished<br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| Lower　the priority<br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| Lower　the priority<br />
|-<br />
|- style="background:silver"<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|--style="background:silver"<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
| 2016/3/27<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
|Fix confirmed (2016/3/30).<br />
|-<br />
|-style="background:silver"<br />
| 18<br />
| Buildfarm not working<br />
| 2016/3/16<br />
|<br />
| Yugo<br />
|<br />
| Should be fixed as soon as possible. It turned out that it was caused by disk full.<br />
|-style="background:silver"<br />
| 19<br />
| failback_command finishes,pgpool-II DONNOT restart all child processes<br />
| 2016/3/18<br />
|<br />
| Usama<br />
|http://www.pgpool.net/mantisbt/view.php?id=172<br />
|<br />
|-style="background:silver"<br />
| 20<br />
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=174<br />
|<br />
|-style="background:silver"<br />
| 21<br />
| find_primay_node fails to find the primary node<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
|pgpool-general: 4560<br />
|Waiting for feedback but no response since 2016/3/30. So close this now...<br />
|-style="background:silver"<br />
| 22<br />
| kind mismatch among backends with COMMIT;<br />
| 2016/3/23<br />
|<br />
| Usama<br />
|pgpool-general: 4565<br />
|Waiting for feedback.-> no reply since 2016/3/24. Closed<br />
|-style="background:silver"<br />
| 23<br />
| Error with JDBC memory_cache_enabled = on<br />
| 2016/3/22<br />
| 2016/5/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=152<br />
| resolved on 2016/5/21<br />
|-style="background:silver"<br />
| 24<br />
| Enironment Variable PG_CONFIG Ignored<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=178<br />
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.<br />
|-style="background:silver"<br />
| 25<br />
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS<br />
| 2016/3/23<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=179<br />
| Responded back, nothing to be done for that<br />
|-style="background:silver"<br />
| 26<br />
| regression test failure with 004.watchdog<br />
| 2016/3/22<br />
|<br />
| Usama<br />
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac<br />
| 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.<br />
|-style="background:silver"<br />
| 27<br />
| Pgpool child hangs with full cpu load after permission error message from backend<br />
| 2016/3/24<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=182<br />
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29<br />
|-style="background:yellow"<br />
| 28<br />
| Online recovery: existing connections did not close in 90 sec.<br />
| 2016/3/23<br />
| 2016/4/30<br />
| Tatsuo<br />
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)<br />
| [in progress]<br />
|-style="background:silver"<br />
| 29<br />
| Pgppol not sending query error back to client<br />
| 2016/3/25<br />
| 2016/6/21<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=183<br />
| [in progress] Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28<br />
|-style="background:silver"<br />
| 30<br />
| PGPoolII-3.5 : segfault during pcp_recovery<br />
| 2016/3/23<br />
| 2016/4/4<br />
| Usama<br />
| pgpool-general: 4569<br />
| fixed commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9<br />
|-style="background:silver"<br />
| 31<br />
| pgpool-II minor releases<br />
| <br />
| 2016/4/4<br />
| Yugo<br />
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1<br />
|<br />
|-style="background:silver"<br />
| 32<br />
| plugs out the network cable，the pgpool will not work。<br />
| 2016/3/28<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=185<br />
| <br />
|-style="background:silver"<br />
| 33<br />
| Hibernate + Pgpool-II Connection Failure<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=175<br />
| Fix confirmed (in 3.5.1)<br />
|-style="background:silver"<br />
| 34<br />
| What is the execution order of ‘follow_master_command' and 'failover_command'?<br />
| 2016/3/19<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=176<br />
| Waiting for feedback -> No feedback for a month. Close now...<br />
|-style="background:silver"<br />
| 35<br />
| Pgpool stops accepting connections when Postgresql slave goes down<br />
| 2016/3/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=177<br />
| Should be already fixed. [pgpool-hackers: 1531]<br />
|-style="background:silver"<br />
| 36<br />
| pcp_proc_count truncates PIDs over 5 characters long<br />
| 2016/4/6<br />
| 2016/4/20<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=188<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bd11fcf420fe0e9cd1705673b0594aab39307cb9<br />
|-style="background:silver"<br />
| 37<br />
| pgpool web console gets pgpool.conf parameters incorrectly<br />
| 2016/4/7<br />
|<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=158<br />
| assigned [Pgpool:1102] Bug 158-->assign changed to Nozomi because this is an pgpoolAdmin issue<br />
|-style="background:silver"<br />
| 38<br />
| Always PostgreSQL1 node is down frequently from PGpool console<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=161<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 39<br />
| Connections not released if client exit ungracefully<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=163<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 40<br />
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism<br />
| 2016/4/7<br />
| 2016/4/11<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=187<br />
| fix committed<br />
|-style="background:silver"<br />
| 41<br />
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off<br />
| 2016/4/8<br />
| 2016/4/15<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=189<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=a3227199ddb688c54d8170c2f12f14cf041a43ab<br />
|-style="background:silver"<br />
| 42<br />
| PgPool hangs in load balance mode, when using JDBC driver and sending empty query<br />
| 2016/4/11<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=190<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=a5fdf78e6e86c5a8a1d4ce5b1eb273a59f5ecfb9<br />
|-style="background:silver"<br />
| 43<br />
| pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves<br />
| 2016/4/14<br />
| 2016/5/09<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=191<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f97aa57fa89bd5c57dafb74f07e5531009d2391c<br />
|-style="background:silver"<br />
| 44<br />
| kind does not match error in pgpool [pgpool-hackers:1501]<br />
| 2016/4/20<br />
| 2016/7/15<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2016-April/001501.html<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=866575c8fe89da2127a6c1bb19746b03b61bbfd4<br />
|-style="background:silver"<br />
| 45<br />
| ERROR: unable to read data from frontend [pgpool-general: 4662]<br />
| 2016/5/9<br />
| 2016/5/11<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004720.html<br />
| The problem isn't reproducable. [Pgpool:1248] <br />
|-style="background:silver"<br />
| 46<br />
| pgpool error with PAM [pgpool-general: 4670]<br />
| 2016/5/10<br />
| 2016/5/11<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004728.html<br />
| No response yet. [Pgpool:1248] <br />
|-style="background:silver"<br />
| 47<br />
| New Defects reported by Coverity Scan for pgpool-II [Pgpool:1227]<br />
| 2016/5/11<br />
| 2016/06/21<br />
| Usama<br />
| [Pgpool:1227]<br />
| changes committed waiting for new scan<br />
|-style="background:silver"<br />
| 48<br />
| "statement timeout" causes kind mismatch errors<br />
| 2016/5/16<br />
|<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=194<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=efb2162215f0a99103a49c0094da825640ff036f<br />
|-<br />
| 49<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| low priority<br />
|-style="background:silver"<br />
| 50<br />
| pgpool hangs connections to database when interface of standby/second backend<br />
| 2016/5/23<br />
| 2016/6/10<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=197<br />
| fixed git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=6ae42e74d48391b8cfaa97927e00bd65aec68fe8<br />
|-<br />
| 51<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| in progress<br />
|-style="background:silver"<br />
| 52<br />
| healthcheck get stuck<br />
| 2016/6/2<br />
| 2016/6/10<br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=204<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=634c1d6c01234b773002ceb763eeba4bc6b83206<br />
|-<br />
| 53<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/7/22<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| feedback<br />
|-<br />
| 54<br />
| testing of new failover code<br />
| 2016/6/6<br />
| <br />
| Ahsan<br />
|<br />
| assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 55<br />
| Re: [pgpool-II 0000192]: Human readable option for pcp_node_info<br />
| 2016/6/10<br />
| 2016/7/30<br />
| Usama<br />
|<br />
| assigned<br />
|-<br />
| 56<br />
| pgpool runs out of memory<br />
| 2016/7/4<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=212<br />
| waiting for feedback<br />
|-<br />
| 57<br />
| Cannot accept() new connection. all backends are down restart<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=205<br />
| waiting for feedback<br />
|-<br />
| 58<br />
| write on frontend failed with error :"Broken pipe"<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=206<br />
| waiting for feedback<br />
|-<br />
| 59<br />
| Query cache invalidation performed too late<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=209<br />
| assigned<br />
|-style="background:silver"<br />
| 60<br />
| received degenerate backend request for node_id:<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=210<br />
| fixed<br />
|-<br />
| 61<br />
| YCSB can't connect to PGPool-II in master-slave mode.<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=211<br />
| waiting for feedback<br />
|-<br />
| 62<br />
| [pgpool-general: 4761] show pool_nodes returns different result when run on master and on slave<br />
| 2016/7/7<br />
|<br />
| Usama<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-July/004819.html <br />
| assigned<br />
|-<br />
| 63<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| waiting for feedback<br />
|-<br />
| 64<br />
| plugs out the network cable, pgpool not change backend status and blocking connections<br />
| 2016/7/5<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=214<br />
| waiting for feedback<br />
|-<br />
| 65<br />
| pgpool doesnt escalate ip in case of another node inavailability<br />
| 2016/7/12<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=215<br />
| waiting for feedback<br />
|-style="background:yellow"<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| 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.<br />
|-style="background:yellow"<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1517
pgpool-II 3.6 development
2016-07-21T19:47:21Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/7/15 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-style="background:silver"<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| 2016/07/08<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6. Usama will review this until 12 June.　follow up by Usama in [pgpool-general: 4721] http://www.pgpool.net/pipermail/pgpool-general/2016-June/004779.html -- done on 2016/07/12<br />
|-style="background:silver"<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| 2016/5/13<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6, strongly connected to item 11.--> Not necessary any more.<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| [in progress] Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| 2016/07/25<br />
| Usama<br />
| deal with pg_terminate_backend<br />
| in progress need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| 2016/8/31<br />
| Peng<br />
| <br />
| [In progress] Will start after PostgreSQL 9.6 beta released<br />
|-style="background:silver"<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/5/19<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly. Done on 2016/5/21.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 9-4<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/27<br />
| 2016/8/31<br />
| Tatsuo, Peng, Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| [in progress] See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/<br />
|-<br />
| 9-5<br />
| Convert the pgpool documentation to SGML (Tatsuo)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Tatsuo<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| [in progress] See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Preface, Tutorial.Getting Started, Server Administration.pgpool-II Installation from Source Code, Server Administration.Server Setup and Operation<br />
|-<br />
| 9-6<br />
| Convert the pgpool documentation to SGML (Usama)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Tutorial.Watchdog, Server Administration.Server Configuration, Server Administration.Client Authentication, Examples<br />
|-<br />
| 9-7<br />
| Convert the pgpool documentation to SGML (Pengbo)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Pengbo<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Reference<br />
|- style="background:white"<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| Lower　the priority<br />
|-style="background:silver"<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/5/13<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted. At this point pcp_detach_node does not break in certain cases (load balance node is not detached)<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| Will do after #8 and #8 are finished<br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| Lower　the priority<br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| Lower　the priority<br />
|-<br />
|- style="background:silver"<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|--style="background:silver"<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
| 2016/3/27<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
|Fix confirmed (2016/3/30).<br />
|-<br />
|-style="background:silver"<br />
| 18<br />
| Buildfarm not working<br />
| 2016/3/16<br />
|<br />
| Yugo<br />
|<br />
| Should be fixed as soon as possible. It turned out that it was caused by disk full.<br />
|-style="background:silver"<br />
| 19<br />
| failback_command finishes,pgpool-II DONNOT restart all child processes<br />
| 2016/3/18<br />
|<br />
| Usama<br />
|http://www.pgpool.net/mantisbt/view.php?id=172<br />
|<br />
|-style="background:silver"<br />
| 20<br />
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=174<br />
|<br />
|-style="background:silver"<br />
| 21<br />
| find_primay_node fails to find the primary node<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
|pgpool-general: 4560<br />
|Waiting for feedback but no response since 2016/3/30. So close this now...<br />
|-style="background:silver"<br />
| 22<br />
| kind mismatch among backends with COMMIT;<br />
| 2016/3/23<br />
|<br />
| Usama<br />
|pgpool-general: 4565<br />
|Waiting for feedback.-> no reply since 2016/3/24. Closed<br />
|-style="background:silver"<br />
| 23<br />
| Error with JDBC memory_cache_enabled = on<br />
| 2016/3/22<br />
| 2016/5/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=152<br />
| resolved on 2016/5/21<br />
|-style="background:silver"<br />
| 24<br />
| Enironment Variable PG_CONFIG Ignored<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=178<br />
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.<br />
|-style="background:silver"<br />
| 25<br />
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS<br />
| 2016/3/23<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=179<br />
| Responded back, nothing to be done for that<br />
|-style="background:silver"<br />
| 26<br />
| regression test failure with 004.watchdog<br />
| 2016/3/22<br />
|<br />
| Usama<br />
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac<br />
| 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.<br />
|-style="background:silver"<br />
| 27<br />
| Pgpool child hangs with full cpu load after permission error message from backend<br />
| 2016/3/24<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=182<br />
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29<br />
|-style="background:yellow"<br />
| 28<br />
| Online recovery: existing connections did not close in 90 sec.<br />
| 2016/3/23<br />
| 2016/4/30<br />
| Tatsuo<br />
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)<br />
| [in progress]<br />
|-style="background:silver"<br />
| 29<br />
| Pgppol not sending query error back to client<br />
| 2016/3/25<br />
| 2016/6/21<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=183<br />
| [in progress] Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28<br />
|-style="background:silver"<br />
| 30<br />
| PGPoolII-3.5 : segfault during pcp_recovery<br />
| 2016/3/23<br />
| 2016/4/4<br />
| Usama<br />
| pgpool-general: 4569<br />
| fixed commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9<br />
|-style="background:silver"<br />
| 31<br />
| pgpool-II minor releases<br />
| <br />
| 2016/4/4<br />
| Yugo<br />
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1<br />
|<br />
|-style="background:silver"<br />
| 32<br />
| plugs out the network cable，the pgpool will not work。<br />
| 2016/3/28<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=185<br />
| <br />
|-style="background:silver"<br />
| 33<br />
| Hibernate + Pgpool-II Connection Failure<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=175<br />
| Fix confirmed (in 3.5.1)<br />
|-style="background:silver"<br />
| 34<br />
| What is the execution order of ‘follow_master_command' and 'failover_command'?<br />
| 2016/3/19<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=176<br />
| Waiting for feedback -> No feedback for a month. Close now...<br />
|-style="background:silver"<br />
| 35<br />
| Pgpool stops accepting connections when Postgresql slave goes down<br />
| 2016/3/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=177<br />
| Should be already fixed. [pgpool-hackers: 1531]<br />
|-style="background:silver"<br />
| 36<br />
| pcp_proc_count truncates PIDs over 5 characters long<br />
| 2016/4/6<br />
| 2016/4/20<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=188<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bd11fcf420fe0e9cd1705673b0594aab39307cb9<br />
|-style="background:silver"<br />
| 37<br />
| pgpool web console gets pgpool.conf parameters incorrectly<br />
| 2016/4/7<br />
|<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=158<br />
| assigned [Pgpool:1102] Bug 158-->assign changed to Nozomi because this is an pgpoolAdmin issue<br />
|-style="background:silver"<br />
| 38<br />
| Always PostgreSQL1 node is down frequently from PGpool console<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=161<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 39<br />
| Connections not released if client exit ungracefully<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=163<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 40<br />
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism<br />
| 2016/4/7<br />
| 2016/4/11<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=187<br />
| fix committed<br />
|-style="background:silver"<br />
| 41<br />
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off<br />
| 2016/4/8<br />
| 2016/4/15<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=189<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=a3227199ddb688c54d8170c2f12f14cf041a43ab<br />
|-style="background:silver"<br />
| 42<br />
| PgPool hangs in load balance mode, when using JDBC driver and sending empty query<br />
| 2016/4/11<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=190<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=a5fdf78e6e86c5a8a1d4ce5b1eb273a59f5ecfb9<br />
|-style="background:silver"<br />
| 43<br />
| pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves<br />
| 2016/4/14<br />
| 2016/5/09<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=191<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f97aa57fa89bd5c57dafb74f07e5531009d2391c<br />
|-style="background:silver"<br />
| 44<br />
| kind does not match error in pgpool [pgpool-hackers:1501]<br />
| 2016/4/20<br />
| 2016/7/15<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2016-April/001501.html<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=866575c8fe89da2127a6c1bb19746b03b61bbfd4<br />
|-style="background:silver"<br />
| 45<br />
| ERROR: unable to read data from frontend [pgpool-general: 4662]<br />
| 2016/5/9<br />
| 2016/5/11<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004720.html<br />
| The problem isn't reproducable. [Pgpool:1248] <br />
|-style="background:silver"<br />
| 46<br />
| pgpool error with PAM [pgpool-general: 4670]<br />
| 2016/5/10<br />
| 2016/5/11<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004728.html<br />
| No response yet. [Pgpool:1248] <br />
|-style="background:silver"<br />
| 47<br />
| New Defects reported by Coverity Scan for pgpool-II [Pgpool:1227]<br />
| 2016/5/11<br />
| 2016/06/21<br />
| Usama<br />
| [Pgpool:1227]<br />
| changes committed waiting for new scan<br />
|-style="background:silver"<br />
| 48<br />
| "statement timeout" causes kind mismatch errors<br />
| 2016/5/16<br />
|<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=194<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=efb2162215f0a99103a49c0094da825640ff036f<br />
|-<br />
| 49<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| low priority<br />
|-style="background:silver"<br />
| 50<br />
| pgpool hangs connections to database when interface of standby/second backend<br />
| 2016/5/23<br />
| 2016/6/10<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=197<br />
| fixed git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=6ae42e74d48391b8cfaa97927e00bd65aec68fe8<br />
|-<br />
| 51<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| 2016/7/26<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| in progress<br />
|-style="background:silver"<br />
| 52<br />
| healthcheck get stuck<br />
| 2016/6/2<br />
| 2016/6/10<br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=204<br />
| fixed https://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=634c1d6c01234b773002ceb763eeba4bc6b83206<br />
|-<br />
| 53<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/7/22<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| feedback<br />
|-<br />
| 54<br />
| testing of new failover code<br />
| 2016/6/6<br />
| <br />
| Ahsan<br />
|<br />
| assigned (Not started yet, plan to start after #04)<br />
|-<br />
| 55<br />
| Re: [pgpool-II 0000192]: Human readable option for pcp_node_info<br />
| 2016/6/10<br />
| 2016/6/30<br />
| Usama<br />
|<br />
| assigned<br />
|-<br />
| 56<br />
| pgpool runs out of memory<br />
| 2016/7/4<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=212<br />
| waiting for feedback<br />
|-<br />
| 57<br />
| Cannot accept() new connection. all backends are down restart<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=205<br />
| waiting for feedback<br />
|-<br />
| 58<br />
| write on frontend failed with error :"Broken pipe"<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=206<br />
| waiting for feedback<br />
|-<br />
| 59<br />
| Query cache invalidation performed too late<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=209<br />
| assigned<br />
|-style="background:silver"<br />
| 60<br />
| received degenerate backend request for node_id:<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=210<br />
| fixed<br />
|-<br />
| 61<br />
| YCSB can't connect to PGPool-II in master-slave mode.<br />
| 2016/7/4<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=211<br />
| waiting for feedback<br />
|-<br />
| 62<br />
| [pgpool-general: 4761] show pool_nodes returns different result when run on master and on slave<br />
| 2016/7/7<br />
|<br />
| Usama<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-July/004819.html <br />
| assigned<br />
|-<br />
| 63<br />
| ERROR: node recovery failed, waiting connection closed in the other pgpools timeout<br />
| 2016/7/12<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=213 <br />
| waiting for feedback<br />
|-<br />
| 64<br />
| plugs out the network cable, pgpool not change backend status and blocking connections<br />
| 2016/7/5<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=214<br />
| waiting for feedback<br />
|-<br />
| 65<br />
| pgpool doesnt escalate ip in case of another node inavailability<br />
| 2016/7/12<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=215<br />
| waiting for feedback<br />
|-style="background:yellow"<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| 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.<br />
|-style="background:yellow"<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1445
pgpool-II 3.6 development
2016-06-09T21:08:22Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/6/6 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| 2016/06/12<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6. Usama will review this until 12 June.<br />
|-style="background:silver"<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| 2016/5/13<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6, strongly connected to item 11.--> Not necessary any more.<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| 2016/06/17<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| 2016/06/26<br />
| Usama<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| 2016/8/31<br />
| Peng<br />
| <br />
| Will start after PostgreSQL 9.6 beta released<br />
|-style="background:silver"<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/5/19<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly. Done on 2016/5/21.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 9-4<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/27<br />
| 2016/8/31<br />
| Tatsuo, Peng, Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/<br />
|-<br />
| 9-5<br />
| Convert the pgpool documentation to SGML (Tatsuo)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Tatsuo<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Preface, Tutorial.Getting Started, Server Administration.pgpool-II Installation from Source Code, Server Administration.Server Setup and Operation<br />
|-<br />
| 9-6<br />
| Convert the pgpool documentation to SGML (Usama)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Tutorial.Watchdog, Server Administration.Server Configuration, Server Administration.Client Authentication, Examples<br />
|-<br />
| 9-7<br />
| Convert the pgpool documentation to SGML (Pengbo)<br />
| 2016/6/6<br />
| 2016/8/31<br />
| Pengbo<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/ Responsible part: Reference<br />
|- style="background:white"<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| <br />
|-style="background:silver"<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/5/13<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted. At this point pcp_detach_node does not break in certain cases (load balance node is not detached)<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| Will do after #8 and #8 are finished<br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| Lower　the priority<br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| Lower　the priority<br />
|-<br />
|- style="background:silver"<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|--style="background:silver"<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
| 2016/3/27<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
|Fix confirmed (2016/3/30).<br />
|-<br />
|-style="background:silver"<br />
| 18<br />
| Buildfarm not working<br />
| 2016/3/16<br />
|<br />
| Yugo<br />
|<br />
| Should be fixed as soon as possible. It turned out that it was caused by disk full.<br />
|-style="background:silver"<br />
| 19<br />
| failback_command finishes,pgpool-II DONNOT restart all child processes<br />
| 2016/3/18<br />
|<br />
| Usama<br />
|http://www.pgpool.net/mantisbt/view.php?id=172<br />
|<br />
|-style="background:silver"<br />
| 20<br />
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=174<br />
|<br />
|-style="background:silver"<br />
| 21<br />
| find_primay_node fails to find the primary node<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
|pgpool-general: 4560<br />
|Waiting for feedback but no response since 2016/3/30. So close this now...<br />
|-style="background:silver"<br />
| 22<br />
| kind mismatch among backends with COMMIT;<br />
| 2016/3/23<br />
|<br />
| Usama<br />
|pgpool-general: 4565<br />
|Waiting for feedback.-> no reply since 2016/3/24. Closed<br />
|-style="background:silver"<br />
| 23<br />
| Error with JDBC memory_cache_enabled = on<br />
| 2016/3/22<br />
| 2016/5/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=152<br />
| resolved on 2016/5/21<br />
|-style="background:silver"<br />
| 24<br />
| Enironment Variable PG_CONFIG Ignored<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=178<br />
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.<br />
|-style="background:silver"<br />
| 25<br />
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS<br />
| 2016/3/23<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=179<br />
| Responded back, nothing to be done for that<br />
|-style="background:silver"<br />
| 26<br />
| regression test failure with 004.watchdog<br />
| 2016/3/22<br />
|<br />
| Usama<br />
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac<br />
| 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.<br />
|-style="background:silver"<br />
| 27<br />
| Pgpool child hangs with full cpu load after permission error message from backend<br />
| 2016/3/24<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=182<br />
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29<br />
|-style="background:yellow"<br />
| 28<br />
| Online recovery: existing connections did not close in 90 sec.<br />
| 2016/3/23<br />
| 2016/4/30<br />
| Tatsuo<br />
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)<br />
|<br />
|-style="background:silver"<br />
| 29<br />
| Pgppol not sending query error back to client<br />
| 2016/3/25<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=183<br />
| Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28<br />
|-style="background:silver"<br />
| 30<br />
| PGPoolII-3.5 : segfault during pcp_recovery<br />
| 2016/3/23<br />
| 2016/4/4<br />
| Usama<br />
| pgpool-general: 4569<br />
| fixed commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9<br />
|-style="background:silver"<br />
| 31<br />
| pgpool-II minor releases<br />
| <br />
| 2016/4/4<br />
| Yugo<br />
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1<br />
|<br />
|-style="background:silver"<br />
| 32<br />
| plugs out the network cable，the pgpool will not work。<br />
| 2016/3/28<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=185<br />
| <br />
|-style="background:silver"<br />
| 33<br />
| Hibernate + Pgpool-II Connection Failure<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=175<br />
| Fix confirmed (in 3.5.1)<br />
|-style="background:silver"<br />
| 34<br />
| What is the execution order of ‘follow_master_command' and 'failover_command'?<br />
| 2016/3/19<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=176<br />
| Waiting for feedback -> No feedback for a month. Close now...<br />
|-style="background:silver"<br />
| 35<br />
| Pgpool stops accepting connections when Postgresql slave goes down<br />
| 2016/3/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=177<br />
| Should be already fixed. [pgpool-hackers: 1531]<br />
|-style="background:silver"<br />
| 36<br />
| pcp_proc_count truncates PIDs over 5 characters long<br />
| 2016/4/6<br />
| 2016/4/20<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=188<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bd11fcf420fe0e9cd1705673b0594aab39307cb9<br />
|-style="background:silver"<br />
| 37<br />
| pgpool web console gets pgpool.conf parameters incorrectly<br />
| 2016/4/7<br />
|<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=158<br />
| assigned [Pgpool:1102] Bug 158-->assign changed to Nozomi because this is an pgpoolAdmin issue<br />
|-style="background:silver"<br />
| 38<br />
| Always PostgreSQL1 node is down frequently from PGpool console<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=161<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 39<br />
| Connections not released if client exit ungracefully<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=163<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 40<br />
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism<br />
| 2016/4/7<br />
| 2016/4/11<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=187<br />
| fix committed<br />
|-style="background:silver"<br />
| 41<br />
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off<br />
| 2016/4/8<br />
| 2016/4/15<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=189<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=a3227199ddb688c54d8170c2f12f14cf041a43ab<br />
|-style="background:silver"<br />
| 42<br />
| PgPool hangs in load balance mode, when using JDBC driver and sending empty query<br />
| 2016/4/11<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=190<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=a5fdf78e6e86c5a8a1d4ce5b1eb273a59f5ecfb9<br />
|-style="background:silver"<br />
| 43<br />
| pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves<br />
| 2016/4/14<br />
| 2016/5/09<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=191<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f97aa57fa89bd5c57dafb74f07e5531009d2391c<br />
|-<br />
| 44<br />
| kind does not match error in pgpool [pgpool-hackers:1501]<br />
| 2016/4/20<br />
| 2016/7/15<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2016-April/001501.html<br />
| assigned<br />
|-style="background:silver"<br />
| 45<br />
| ERROR: unable to read data from frontend [pgpool-general: 4662]<br />
| 2016/5/9<br />
| 2016/5/11<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004720.html<br />
| The problem isn't reproducable. [Pgpool:1248] <br />
|-style="background:silver"<br />
| 46<br />
| pgpool error with PAM [pgpool-general: 4670]<br />
| 2016/5/10<br />
| 2016/5/11<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004728.html<br />
| No response yet. [Pgpool:1248] <br />
|-<br />
| 47<br />
| New Defects reported by Coverity Scan for pgpool-II [Pgpool:1227]<br />
| 2016/5/11<br />
|<br />
| Usama<br />
| [Pgpool:1227]<br />
| changes committed waiting for new scan<br />
|-style="background:silver"<br />
| 48<br />
| "statement timeout" causes kind mismatch errors<br />
| 2016/5/16<br />
|<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=194<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=efb2162215f0a99103a49c0094da825640ff036f<br />
|-<br />
| 49<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| assigned<br />
|-<br />
| 50<br />
| pgpool hangs connections to database when interface of standby/second backend<br />
| 2016/5/23<br />
| 2016/6/10<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=197<br />
| assigned<br />
|-<br />
| 51<br />
| Connections stuck - Recv-Q fills up<br />
| 2016/6/2<br />
| <br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=203<br />
| assigned<br />
|-<br />
| 52<br />
| healthcheck get stuck<br />
| 2016/6/2<br />
| <br />
| Yugo<br />
| http://www.pgpool.net/mantisbt/view.php?id=204<br />
| in progress<br />
|-<br />
| 53<br />
| failed to create INET domain socket<br />
| 2016/6/2<br />
| 2016/6/10<br />
| pengbo<br />
| http://www.pgpool.net/mantisbt/view.php?id=202<br />
| assigned<br />
|-<br />
| 54<br />
| testing of new failover code<br />
| 2016/6/6<br />
| <br />
| Ahsan<br />
|<br />
| assigned<br />
|-<br />
| 55<br />
| Re: [pgpool-II 0000192]: Human readable option for pcp_node_info<br />
| 2016/6/10<br />
| 2016/6/30<br />
| Usama<br />
|<br />
| assigned<br />
|-style="background:yellow"<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| 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.<br />
|-style="background:yellow"<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1435
pgpool-II 3.6 development
2016-05-26T08:55:48Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/5/26 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6. Usama will review this.<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| 2016/5/13<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6, strongly connected to item 11.<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| 2016/06/26<br />
| Usama<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| 2016/8/31<br />
| Peng<br />
| <br />
| Will start after PostgreSQL 9.6 beta released<br />
|-style="background:silver"<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/5/19<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly. Done on 2016/5/21.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 9-4<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/27<br />
| 2016/8/31<br />
| Tatsuo, Peng, Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
| See compiled HTML files here: http://tatsuo-ishii.github.io/pgpool-II/3.6/<br />
|- style="background:white"<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| <br />
|-style="background:silver"<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/5/13<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted. At this point pcp_detach_node does not break in certain cases (load balance node is not detached)<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| Will do after #8 and #8 are finished<br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| <br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| <br />
|-<br />
|- style="background:silver"<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|--style="background:silver"<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
| 2016/3/27<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
|Fix confirmed (2016/3/30).<br />
|-<br />
|-style="background:silver"<br />
| 18<br />
| Buildfarm not working<br />
| 2016/3/16<br />
|<br />
| Yugo<br />
|<br />
| Should be fixed as soon as possible. It turned out that it was caused by disk full.<br />
|-style="background:silver"<br />
| 19<br />
| failback_command finishes,pgpool-II DONNOT restart all child processes<br />
| 2016/3/18<br />
|<br />
| Usama<br />
|http://www.pgpool.net/mantisbt/view.php?id=172<br />
|<br />
|-style="background:silver"<br />
| 20<br />
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=174<br />
|<br />
|-style="background:silver"<br />
| 21<br />
| find_primay_node fails to find the primary node<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
|pgpool-general: 4560<br />
|Waiting for feedback but no response since 2016/3/30. So close this now...<br />
|-style="background:silver"<br />
| 22<br />
| kind mismatch among backends with COMMIT;<br />
| 2016/3/23<br />
|<br />
| Usama<br />
|pgpool-general: 4565<br />
|Waiting for feedback.-> no reply since 2016/3/24. Closed<br />
|-style="background:silver"<br />
| 23<br />
| Error with JDBC memory_cache_enabled = on<br />
| 2016/3/22<br />
| 2016/5/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=152<br />
| resolved on 2016/5/21<br />
|-style="background:silver"<br />
| 24<br />
| Enironment Variable PG_CONFIG Ignored<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=178<br />
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.<br />
|-style="background:silver"<br />
| 25<br />
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS<br />
| 2016/3/23<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=179<br />
| Responded back, nothing to be done for that<br />
|-style="background:silver"<br />
| 26<br />
| regression test failure with 004.watchdog<br />
| 2016/3/22<br />
|<br />
| Usama<br />
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac<br />
| 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.<br />
|-style="background:silver"<br />
| 27<br />
| Pgpool child hangs with full cpu load after permission error message from backend<br />
| 2016/3/24<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=182<br />
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29<br />
|-style="background:yellow"<br />
| 28<br />
| Online recovery: existing connections did not close in 90 sec.<br />
| 2016/3/23<br />
| 2016/4/30<br />
| Tatsuo<br />
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)<br />
|<br />
|-style="background:silver"<br />
| 29<br />
| Pgppol not sending query error back to client<br />
| 2016/3/25<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=183<br />
| Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28<br />
|-style="background:silver"<br />
| 30<br />
| PGPoolII-3.5 : segfault during pcp_recovery<br />
| 2016/3/23<br />
| 2016/4/4<br />
| Usama<br />
| pgpool-general: 4569<br />
| fixed commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9<br />
|-style="background:silver"<br />
| 31<br />
| pgpool-II minor releases<br />
| <br />
| 2016/4/4<br />
| Yugo<br />
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1<br />
|<br />
|-style="background:silver"<br />
| 32<br />
| plugs out the network cable，the pgpool will not work。<br />
| 2016/3/28<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=185<br />
| <br />
|-style="background:silver"<br />
| 33<br />
| Hibernate + Pgpool-II Connection Failure<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=175<br />
| Fix confirmed (in 3.5.1)<br />
|-style="background:silver"<br />
| 34<br />
| What is the execution order of ‘follow_master_command' and 'failover_command'?<br />
| 2016/3/19<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=176<br />
| Waiting for feedback -> No feedback for a month. Close now...<br />
|-style="background:silver"<br />
| 35<br />
| Pgpool stops accepting connections when Postgresql slave goes down<br />
| 2016/3/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=177<br />
| Should be already fixed. [pgpool-hackers: 1531]<br />
|-style="background:silver"<br />
| 36<br />
| pcp_proc_count truncates PIDs over 5 characters long<br />
| 2016/4/6<br />
| 2016/4/20<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=188<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bd11fcf420fe0e9cd1705673b0594aab39307cb9<br />
|-style="background:silver"<br />
| 37<br />
| pgpool web console gets pgpool.conf parameters incorrectly<br />
| 2016/4/7<br />
|<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=158<br />
| assigned [Pgpool:1102] Bug 158-->assign changed to Nozomi because this is an pgpoolAdmin issue<br />
|-style="background:silver"<br />
| 38<br />
| Always PostgreSQL1 node is down frequently from PGpool console<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=161<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 39<br />
| Connections not released if client exit ungracefully<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=163<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 40<br />
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism<br />
| 2016/4/7<br />
| 2016/4/11<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=187<br />
| fix committed<br />
|-style="background:silver"<br />
| 41<br />
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off<br />
| 2016/4/8<br />
| 2016/4/15<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=189<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=a3227199ddb688c54d8170c2f12f14cf041a43ab<br />
|-style="background:silver"<br />
| 42<br />
| PgPool hangs in load balance mode, when using JDBC driver and sending empty query<br />
| 2016/4/11<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=190<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=a5fdf78e6e86c5a8a1d4ce5b1eb273a59f5ecfb9<br />
|-style="background:silver"<br />
| 43<br />
| pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves<br />
| 2016/4/14<br />
| 2016/5/09<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=191<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f97aa57fa89bd5c57dafb74f07e5531009d2391c<br />
|-<br />
| 44<br />
| kind does not match error in pgpool [pgpool-hackers:1501]<br />
| 2016/4/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2016-April/001501.html<br />
| assigned<br />
|-<br />
| 45<br />
| ERROR: unable to read data from frontend [pgpool-general: 4662]<br />
| 2016/5/9<br />
|<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004720.html<br />
| assigned<br />
|-<br />
| 46<br />
| pgpool error with PAM [pgpool-general: 4670]<br />
| 2016/5/10<br />
|<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004728.html<br />
| assigned<br />
|-<br />
| 47<br />
| New Defects reported by Coverity Scan for pgpool-II [Pgpool:1227]<br />
| 2016/5/11<br />
|<br />
| Usama<br />
| [Pgpool:1227]<br />
| changes committed waiting for new scan<br />
|-style="background:silver"<br />
| 48<br />
| "statement timeout" causes kind mismatch errors<br />
| 2016/5/16<br />
|<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=194<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=efb2162215f0a99103a49c0094da825640ff036f<br />
|-<br />
| 49<br />
| pgpool routes queries with "SET TRANSACTION READ ONLY" to master<br />
| 2016/5/18<br />
| 2016/6/30<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=195<br />
| assigned<br />
|-<br />
| 50<br />
| pgpool hangs connections to database when interface of standby/second backend<br />
| 2016/5/23<br />
| 2016/5/31<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=197<br />
| assigned<br />
|-style="background:yellow"<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| 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.<br />
|-style="background:yellow"<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1421
pgpool-II 3.6 development
2016-05-11T11:18:00Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/5/11 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6. Usama will review this.<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| 2016/5/13<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6, strongly connected to item 11.<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| -<br />
| Usama<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| -<br />
| Peng<br />
| <br />
| Will start after PostgreSQL 9.6 beta released<br />
|-style="background:yellow"<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/5/19<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 9-4<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/27<br />
|<br />
| Tatsuo, Peng, Usama<br />
| Create/migrate actual pgpool-II document in SGML format<br />
|<br />
|-<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| <br />
|-style="background:silver"<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/5/13<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted. At this point pcp_detach_node does not break in certain cases (load balance node is not detached)<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| Will do after #8 and #8 are finished<br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| <br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| <br />
|-<br />
|- style="background:silver"<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|--style="background:silver"<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
| 2016/3/27<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
|Fix confirmed (2016/3/30).<br />
|-<br />
|-style="background:silver"<br />
| 18<br />
| Buildfarm not working<br />
| 2016/3/16<br />
|<br />
| Yugo<br />
|<br />
| Should be fixed as soon as possible. It turned out that it was caused by disk full.<br />
|-style="background:silver"<br />
| 19<br />
| failback_command finishes,pgpool-II DONNOT restart all child processes<br />
| 2016/3/18<br />
|<br />
| Usama<br />
|http://www.pgpool.net/mantisbt/view.php?id=172<br />
|<br />
|-style="background:silver"<br />
| 20<br />
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=174<br />
|<br />
|-style="background:silver"<br />
| 21<br />
| find_primay_node fails to find the primary node<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
|pgpool-general: 4560<br />
|Waiting for feedback but no response since 2016/3/30. So close this now...<br />
|-<br />
| 22<br />
| kind mismatch among backends with COMMIT;<br />
| 2016/3/23<br />
|<br />
| Usama<br />
|pgpool-general: 4565<br />
|Waiting for feedback.<br />
|-<br />
| 23<br />
| Error with JDBC memory_cache_enabled = on<br />
| 2016/3/22<br />
| 2016/5/31<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=152<br />
| The reporter said it only happens in raw mode and prepare threshold = 1<br />
|-style="background:silver"<br />
| 24<br />
| Enironment Variable PG_CONFIG Ignored<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=178<br />
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.<br />
|-style="background:silver"<br />
| 25<br />
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS<br />
| 2016/3/23<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=179<br />
| Responded back, nothing to be done for that<br />
|-style="background:silver"<br />
| 26<br />
| regression test failure with 004.watchdog<br />
| 2016/3/22<br />
|<br />
| Usama<br />
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac<br />
| 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.<br />
|-style="background:silver"<br />
| 27<br />
| Pgpool child hangs with full cpu load after permission error message from backend<br />
| 2016/3/24<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=182<br />
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29<br />
|-style="background:yellow"<br />
| 28<br />
| Online recovery: existing connections did not close in 90 sec.<br />
| 2016/3/23<br />
| 2016/4/30<br />
| Tatsuo<br />
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)<br />
|<br />
|-style="background:silver"<br />
| 29<br />
| Pgppol not sending query error back to client<br />
| 2016/3/25<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=183<br />
| Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28<br />
|-style="background:silver"<br />
| 30<br />
| PGPoolII-3.5 : segfault during pcp_recovery<br />
| 2016/3/23<br />
| 2016/4/4<br />
| Usama<br />
| pgpool-general: 4569<br />
| fixed commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9<br />
|-style="background:silver"<br />
| 31<br />
| pgpool-II minor releases<br />
| <br />
| 2016/4/4<br />
| Yugo<br />
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1<br />
|<br />
|-style="background:silver"<br />
| 32<br />
| plugs out the network cable，the pgpool will not work。<br />
| 2016/3/28<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=185<br />
| <br />
|-style="background:silver"<br />
| 33<br />
| Hibernate + Pgpool-II Connection Failure<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=175<br />
| Fix confirmed (in 3.5.1)<br />
|-style="background:silver"<br />
| 34<br />
| What is the execution order of ‘follow_master_command' and 'failover_command'?<br />
| 2016/3/19<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=176<br />
| Waiting for feedback -> No feedback for a month. Close now...<br />
|-style="background:white"<br />
| 35<br />
| Pgpool stops accepting connections when Postgresql slave goes down<br />
| 2016/3/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=177<br />
| Should be already fixed. [pgpool-hackers: 1531]<br />
|-style="background:silver"<br />
| 36<br />
| pcp_proc_count truncates PIDs over 5 characters long<br />
| 2016/4/6<br />
| 2016/4/20<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=188<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=bd11fcf420fe0e9cd1705673b0594aab39307cb9<br />
|-style="background:silver"<br />
| 37<br />
| pgpool web console gets pgpool.conf parameters incorrectly<br />
| 2016/4/7<br />
|<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=158<br />
| assigned [Pgpool:1102] Bug 158-->assign changed to Nozomi because this is an pgpoolAdmin issue<br />
|-style="background:silver"<br />
| 38<br />
| Always PostgreSQL1 node is down frequently from PGpool console<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=161<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 39<br />
| Connections not released if client exit ungracefully<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=163<br />
| feedback--> No response over one month. Closed.<br />
|-style="background:silver"<br />
| 40<br />
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism<br />
| 2016/4/7<br />
| 2016/4/11<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=187<br />
| fix committed<br />
|-style="background:silver"<br />
| 41<br />
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off<br />
| 2016/4/8<br />
| 2016/4/15<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=189<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=a3227199ddb688c54d8170c2f12f14cf041a43ab<br />
|-style="background:silver"<br />
| 42<br />
| PgPool hangs in load balance mode, when using JDBC driver and sending empty query<br />
| 2016/4/11<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=190<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=a5fdf78e6e86c5a8a1d4ce5b1eb273a59f5ecfb9<br />
|-style="background:silver"<br />
| 43<br />
| pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves<br />
| 2016/4/14<br />
| 2016/5/09<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=191<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=f97aa57fa89bd5c57dafb74f07e5531009d2391c<br />
|-<br />
| 44<br />
| kind does not match error in pgpoolpgpool-II [pgpool-hackers:1501]<br />
| 2016/4/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/pipermail/pgpool-hackers/2016-April/001501.html<br />
| assigned<br />
|-<br />
| 45<br />
| ERROR: unable to read data from frontend [pgpool-general: 4662]<br />
| 2016/5/9<br />
|<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004720.html<br />
| assigned<br />
|-<br />
| 46<br />
| pgpool error with PAM [pgpool-general: 4670]<br />
| 2016/5/10<br />
|<br />
| Yugo<br />
| http://www.sraoss.jp/pipermail/pgpool-general/2016-May/004728.html<br />
| assigned<br />
|-<br />
| 47<br />
| New Defects reported by Coverity Scan for pgpool-II [Pgpool:1227]<br />
| 2016/5/11<br />
|<br />
| Usama<br />
| [Pgpool:1227]<br />
| assigned<br />
|-<br />
| 48<br />
| "statement timeout" causes kind mismatch errors<br />
| 2016/5/16<br />
|<br />
| t-ishii<br />
| http://www.pgpool.net/mantisbt/view.php?id=194<br />
| assigned<br />
|-style="background:yellow"<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| 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.<br />
|-style="background:yellow"<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1362
pgpool-II 3.6 development
2016-04-15T05:01:57Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/4/14 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| -<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| -<br />
| -<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Start after PostgreSQL 9.6 beta released<br />
|-<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/4/29<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 9-4<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/27<br />
|<br />
|<br />
| Create/migrate actual pgpool-II document in SGML format<br />
|<br />
|-<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| <br />
|-<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/3/31<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| <br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| <br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| <br />
|-<br />
|- style="background:silver"<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|--style="background:silver"<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
| 2016/3/27<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
|Fix confirmed (2016/3/30).<br />
|-<br />
|-style="background:silver"<br />
| 18<br />
| Buildfarm not working<br />
| 2016/3/16<br />
|<br />
| Yugo<br />
|<br />
| Should be fixed as soon as possible. It turned out that it was caused by disk full.<br />
|-style="background:silver"<br />
| 19<br />
| failback_command finishes,pgpool-II DONNOT restart all child processes<br />
| 2016/3/18<br />
|<br />
| Usama<br />
|http://www.pgpool.net/mantisbt/view.php?id=172<br />
|<br />
|-style="background:silver"<br />
| 20<br />
| pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=174<br />
|<br />
|-<br />
| 21<br />
| find_primay_node fails to find the primary node<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
|pgpool-general: 4560<br />
|Waiting for feedback.<br />
|-<br />
| 22<br />
| kind mismatch among backends with COMMIT;<br />
| 2016/3/23<br />
|<br />
| Usama<br />
|pgpool-general: 4565<br />
|Waiting for feedback.<br />
|-<br />
| 23<br />
| Error with JDBC memory_cache_enabled = on<br />
| 2016/3/22<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=152<br />
|Waiting for a feedback<br />
|-style="background:silver"<br />
| 24<br />
| Enironment Variable PG_CONFIG Ignored<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=178<br />
| Topic not suitable for Mantis because it's not related to a bug. I suggested the reporter to move to mailing list.<br />
|-style="background:silver"<br />
| 25<br />
| Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS<br />
| 2016/3/23<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=179<br />
| Responded back, nothing to be done for that<br />
|-style="background:silver"<br />
| 26<br />
| regression test failure with 004.watchdog<br />
| 2016/3/22<br />
|<br />
| Usama<br />
| The test fails Ubuntu after commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=e55c230d674ea221c09e8266a68d119f1a3a2dac<br />
| 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.<br />
|-style="background:silver"<br />
| 27<br />
| Pgpool child hangs with full cpu load after permission error message from backend<br />
| 2016/3/24<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=182<br />
| Already fixed in 3.5 stable tree?->Fix confirmed on 2016/3/29<br />
|-<br />
| 28<br />
| Online recovery: existing connections did not close in 90 sec.<br />
| 2016/3/23<br />
|<br />
| Tatsuo<br />
| pgpool-II 3.3.6, client_idle_limit_in_recovery = -1 doesn't work (pgpool-general: 4570)<br />
|<br />
|-style="background:silver"<br />
| 29<br />
| Pgppol not sending query error back to client<br />
| 2016/3/25<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=183<br />
| Already fixed in 3.5 stable tree? Waiting for feedback->Confirmed on 2016/3/28<br />
|-style="background:silver"<br />
| 30<br />
| PGPoolII-3.5 : segfault during pcp_recovery<br />
| 2016/3/23<br />
| 2016/4/4<br />
| Usama<br />
| pgpool-general: 4569<br />
| fixed commit:http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=64696fd839da70e6fd8daacd73da11b6e8a1f1c9<br />
|-style="background:silver"<br />
| 31<br />
| pgpool-II minor releases<br />
| <br />
| 2016/4/4<br />
| Yugo<br />
| pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, pgpoolAdmin 3.5.1<br />
|<br />
|-style="background:white"<br />
| 32<br />
| plugs out the network cable，the pgpool will not work。<br />
| 2016/3/28<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=185<br />
| <br />
|-style="background:silver"<br />
| 33<br />
| Hibernate + Pgpool-II Connection Failure<br />
| 2016/3/18<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=175<br />
| Fix confirmed (in 3.5.1)<br />
|-style="background:white"<br />
| 34<br />
| What is the execution order of ‘follow_master_command' and 'failover_command'?<br />
| 2016/3/19<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=176<br />
| Waiting for feedback<br />
|-style="background:white"<br />
| 35<br />
| Pgpool stops accepting connections when Postgresql slave goes down<br />
| 2016/3/20<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=177<br />
|<br />
|-<br />
| 36<br />
| pcp_proc_count truncates PIDs over 5 characters long<br />
| 2016/4/6<br />
|<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=188<br />
| In progress<br />
|-<br />
| 37<br />
| pgpool web console gets pgpool.conf parameters incorrectly<br />
| 2016/4/7<br />
|<br />
| Usama<br />
| http://www.pgpool.net/mantisbt/view.php?id=158<br />
| assigned [Pgpool:1102] Bug 158<br />
|-<br />
| 38<br />
| Always PostgreSQL1 node is down frequently from PGpool console<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=161<br />
| feedback<br />
|-<br />
| 39<br />
| Connections not released if client exit ungracefully<br />
| 2016/4/7<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=163<br />
| feedback<br />
|-<br />
| 40<br />
| pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism<br />
| 2016/4/7<br />
|<br />
| Nozomi<br />
| http://www.pgpool.net/mantisbt/view.php?id=187<br />
| assigned <br />
|-<br />
| 41<br />
| kind mismatch error on master_slave_mode=on / load_lalance_mode=off<br />
| 2016/4/8<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=189<br />
| assigned <br />
|-style="background:silver"<br />
| 42<br />
| PgPool hangs in load balance mode, when using JDBC driver and sending empty query<br />
| 2016/4/11<br />
|<br />
| Tatsuo<br />
| http://www.pgpool.net/mantisbt/view.php?id=190<br />
| fixed http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commitdiff;h=a5fdf78e6e86c5a8a1d4ce5b1eb273a59f5ecfb9<br />
|-<br />
| 43<br />
| pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves<br />
| 2016/4/14<br />
|<br />
| Peng<br />
| http://www.pgpool.net/mantisbt/view.php?id=191<br />
| assigned <br />
|-style="background:yellow"<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| 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.<br />
|-style="background:yellow"<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1307
pgpool-II 3.6 development
2016-03-08T13:25:05Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/3/7 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| -<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| -<br />
| -<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Start after PostgreSQL 9.6 beta released<br />
|-<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/4/4<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| <br />
|-<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/3/31<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| <br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| <br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| <br />
|-<br />
|-<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|-<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
| pgpool-II 3.5.1 showstopper<br />
|-<br />
|-<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| All the new platforms that we want to support and add to BF should be decided by this date.<br />
|-<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1306
pgpool-II 3.6 development
2016-03-08T13:13:21Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/3/7 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| -<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| -<br />
| -<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Start after PostgreSQL 9.6 beta released<br />
|-<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| 2016/3/3<br />
| Usama<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|- style="background:silver"<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| Usama<br />
| -<br />
| <br />
|-<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/3/31<br />
| Tatsuo<br />
|http://www.pgpool.net/pipermail/pgpool-hackers/2016-March/001452.html<br />
| Proposal already posted<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| <br />
|-<br />
| 14<br />
| Allow to use multiple pgpool-II instances with in-memory query cache enabled<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Allow_to_use_pg_rewind_in_online_recovery<br />
| <br />
|-<br />
|-<br />
| 15<br />
| Health-check timeout for each backend node<br />
| 2016/3/4<br />
|<br />
|<br />
| http://pgpool.net/mediawiki/index.php/TODO#Health-check_timeout_for_each_backend_node<br />
| <br />
|-<br />
|-<br />
| 16<br />
| Worker Processes Exit and Are Not Re-spawned<br />
| 2016/3/7<br />
|<br />
| Usama<br />
|http://www.pgpool.net/pipermail/pgpool-general/2016-March/004577.html<br />
| <br />
|-<br />
|-<br />
| 17<br />
| Extended query hangs<br />
| 2016/2/22<br />
|<br />
| Tatsuo<br />
|http://www.pgpool.net/mantisbt/view.php?id=167<br />
| pgpool-II 3.5.1 showstopper<br />
|-<br />
|-<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| All the new platforms that we want to support and add to BF should be decided by this date.<br />
|-<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=FAQ&diff=1297
FAQ
2016-03-03T12:24:08Z
<p>Usama: </p>
<hr />
<div>__FORCETOC__<br />
<br />
== Pgpool-II Frequently Asked Questions ==<br />
<br />
=== '''Why configure fails by "pg_config not found" on my Ubuntu box?''' ===<br />
: pg_config is in libpq-dev package. You need to install it before running configure.<br />
<br />
=== '''Why records inserted on the primary node do not appear on the standby nodes?''' ===<br />
: Are you using streaming replication and a hash index on the table? Then it's a known limitation of streaming replication. The inserted record is there. But if you SELECT the record using the hash index, it will not appear. Hash index changes do not produce WAL record thus they are not reflected to the standby nodes. Solutions are: 1) use btree index instead 2) use pgpool-II native replication.<br />
<br />
=== '''Can I mix different versions of PostgreSQL as pgpool-II backends?''' ===<br />
: You cannot mix different major versions of PostgreSQL, for example 8.4.x and 9.0.x. On the other hand you can mix different minor versions of PostgreSQL, for example 9.0.3 and 9.0.4. Pgpool-II assumes messages from PostgreSQL to pgpool-II are identical anytime. Different major version of PostgreSQL may send out different messages and this would cause trouble for Pgpool-II.<br />
<br />
=== '''Can I mix different platforms of PostgreSQL as pgpool-II backends, for example Linux and Windows?''' ===<br />
: In streaming replication mode, no. Because streaming replication requires that primary and standby platforms are phsyically identical. On the other hand, pgpool-II's replication mode only requires logically database clusters identical. Beware, however, that online recovery script does not use rsync or some such, which do phical copying among database clusters. You want to use pg_dumpall instead.<br />
<br />
=== '''It seems my pgpool-II does not do load balancing. Why?''' ===<br />
: First of all, pgpool-II' load balancing is "session base", not "statement base". That means, DB node selection for load balancing is decided at the beginning of session. So all SQL statements are sent to the same DB node until the session ends.<br />
<br />
: Another point is, whether statement is in an explicit transaction or not. If the statement is in a transaction, it will not be load balanced in the replication mode. In pgpool-II 3.0 or later, SELECT will be load balanced even in a transaction if operated in the master/slave mode.<br />
<br />
: Note the method to choose DB node is not LRU or some such. Pgpool-II chooses DB node randomly considering the "weight" parameter in pgpool.conf. This means that the chosen DB node is not uniformly distributed among DB nodes in short term. You might want to inspect the effect of load balancing after ~100 queries have been sent.<br />
<br />
: Also cursor statements are not load balanced in replication mode. i.e.:DECLARE..FETCH are sent to all DB nodes in replication mode. This is because the SELECT might come with FOR UPDATE/FOR SHARE. Note that some applications including psql could use CURSOR for SELECT. For example, from PostgreSQL 8.2, if "\set FETCH_COUNT n" is executed, psql unconditionaly uses a curor named "_psql_cursor".<br />
<br />
=== '''How can I observe the effect of load balancing?''' ===<br />
: We recommend to enable "log_per_node_statement" directive in pgpool.conf for this. Here is an example of the log:<br />
: <pre>2011-05-07 08:42:42 LOG: pid 22382: DB node id: 1 backend pid: 22409 statement: SELECT abalance FROM pgbench_accounts WHERE aid = 62797;</pre><br />
: The "DB node id: 1" shows which DB node was chosen for this loadbalancing session.<br />
<br />
: Please make sure that you start pgpool-II with "-n" option to get pgpool-II log. (or you can use syslog in pgpool-II 3.1 or later)<br />
<br />
=== '''Why am I getting "ProcessFrontendResponse: failed to read kind from frontend. frontend abnormally exited" in my pgool log?''' ===<br />
: Well, your clients might be ill-behaved:-) PostgreSQL's protocol requires clients to send particular packet before they disconnect the connection. pgpool-II complains that clients disconnect without sending the packet. You could reprodcude the problem by using psql. Connect to pgpool using psql. Kill -9 psql. You will silimar message in the log. The message will not appear if you quit psql normaly. Another possibility is unstable network connection between your client machine and pgpool-II. Check the cable and network interface card.<br />
<br />
<br />
=== '''I'm running pgpool-II in streaming replication mode. It seems it works but I find following errors in the log. Why?''' ===<br />
<dl><dd><pre>2011-07-19 08:21:59 ERROR: pid 10727: s_do_auth: unknown response "E" before processing BackendKeyData<br />
2011-07-19 08:21:59 ERROR: pid 10727: s_do_auth: unknown response "" before processing BackendKeyData<br />
2011-07-19 08:21:59 ERROR: pid 10727: s_do_auth: unknown response "" before processing BackendKeyData<br />
2011-07-19 08:21:59 ERROR: pid 10727: s_do_auth: unknown response "" before processing BackendKeyData<br />
2011-07-19 08:21:59 ERROR: pid 10727: s_do_auth: unknown response "[" before processing BackendKeyData<br />
2011-07-19 08:21:59 ERROR: pid 10727: pool_read2: EOF encountered with backend<br />
2011-07-19 08:21:59 ERROR: pid 10727: make_persistent_db_connection: s_do_auth failed<br />
2011-07-19 08:21:59 ERROR: pid 10727: find_primary_node: make_persistent_connection failed</pre></dl><br />
: pgpool-II tries to connect to PostgreSQL to execute some functions such as pg_current_xlog_location(), which is used for detecting primary server or checking replication delay. The messages above indicates that pgpool-II failed to connect with user = health_check_user and password = health_check_password. You need to set them properly even if health_check_period = 0.<br />
<br />
: Note that pgpool-II 3.1 or later will use sr_check_user and sr_check_password for it instead.<br />
<br />
=== '''When I run pgbench to test pgpool-II, pgbench hangs. If I directly run pgbench against PostgreSQL, it works fine. Why?''' ===<br />
: pgbench creates concurrent connections (the number of connections is specified by "-c" option) before starting actual transactions. So if the number of concurrent transactions specified by "-c" exceeds num_init_children, pgbench will stuck because it will wait for pgpool accepting connections forever (remember that pgpool-II accepts up to num_init_children concurrent sessions. If the number of concurrent sessions reach num_init_children, new session will be queued). On the other hand PostgreSQL does not accept concurrent sessions more than max_connections. So in this case you will just see PostgreSQL errors, rather than connection blocking. If you want to test pgpool-II's connection queuing, you can use psql instead of pgbench. In the example session below, num_init_children = 1 (this is not a recommended setting in the real world. This is just for simplicity).<br />
<dl><dd><pre>$ psql test <-- connect to pgpool from terminal #1<br />
psql (9.1.1)<br />
Type "help" for help.<br />
test=# <br />
$ psql test <-- tries to connect to pgpool from terminal #2 but it is blocked.<br />
test=# SELECT 1; <--- do something from terminal #1 psql<br />
test=# \q <-- quit psql session on terminal #1<br />
psql (9.1.1) <-- now psql on terminal #2 accepts session<br />
Type "help" for help.<br />
test=# </pre></dl><br />
=== '''I created pool_hba.conf and pool_passwd to enable md5 authentication through pgpool-II but it does not work. Why?''' ===<br />
: Probably you made mistake somewhere. For your help here is a table which describes error patterns depending on the setting of pg_hba.conf, pool_hba.conf and pool_passwd.<br />
<dl><dd><br />
{|styles="background:white; color:black" border="1"<br />
|-<br />
|pg_hba.conf<br />
|pool_hba.conf<br />
|pool_passwd<br />
|result<br />
|-<br />
|md5<br />
|md5<br />
|yes<br />
|md5 auth<br />
|-<br />
|md5<br />
|md5<br />
|no<br />
|"MD5" authentication with pgpool failed for user "XX"<br />
|-<br />
|md5<br />
|trust<br />
|yes/no<br />
|MD5 authentication is unsupported in replication, master-slave and parallel mode<br />
|-<br />
|trust<br />
|md5<br />
|yes<br />
|no auth<br />
|-<br />
|trust<br />
|md5<br />
|no<br />
|"MD5" authentication with pgpool failed for user "XX"<br />
|-<br />
|trust<br />
|trust<br />
|yes/no<br />
|no auth<br />
|}<br />
</dl><br />
<br />
=== '''How can I set up SSL for pgpool-II?''' ===<br />
<dl><dd>SSL support for pgpool-II consists of two parts: 1)between client and pgpool-II 2)pgpool-II and PostgreSQL. #1 and #2 are independent each other. For example, you can only enable SSL connection of #1, or #2. Or you can enable both #1 and #2. I explain #1 (for #2, please take a look at PostgreSQL documentation).<br />
<br><br />
Make sure that pgpool is built with openssl. If you build from source code, use --with-openssl option.<br />
<br><br />
First create server certificate. In the command below you will be asked PEM pass phrase(It will be asked when pgpool starts up).<br />
If you want to start pgpool without being asked pass phrase, you can remove it later.<br />
([[sample server certficate create session]])<br />
<pre><br />
openssl req -new -text -out server.req<br />
</pre><br />
Remove PEM pass phrase if you want.<br />
<pre><br />
$ openssl rsa -in privkey.pem -out server.key<br />
Enter pass phrase for privkey.pem:<br />
writing RSA key<br />
$ rm privkey.pem<br />
</pre><br />
Turn the certificate into a self-signed certificate.<br />
<pre><br />
$ openssl req -x509 -in server.req -text -key server.key -out server.crt<br />
</pre><br />
Copy server.key and server.crt to appropreate place. Suppose we copy to /usr/local/etc.<br />
Make sure that you use cp -p to retain appropreate permission of server.key.<br />
Alternatively you can set permission later.<br />
<pre><br />
$ chmod og-rwx /usr/local/etc/server.key<br />
</pre><br />
Set the certificate and key location in pgpool.conf.<br />
<pre><br />
ssl = on<br />
ssl_key = '/usr/local/etc/server.key'<br />
ssl_cert = '/usr/local/etc/server.crt'<br />
</pre><br />
Restart pgpool.<br />
To confirm SSL connection between client and pgpool is working, connect to pgpool using psql.<br />
<pre><br />
psql -h localhost -p 9999 test<br />
psql (9.1.1)<br />
SSL connection (cipher: AES256-SHA, bits: 256)<br />
Type "help" for help.<br />
<br />
test=# \q<br />
</pre><br />
If you see "SSL connection...", SSL connection between client and pgpool is working.<br />
Please make sure that use "-h localhost" option. Because SSL only works with TCP/IP,<br />
with Unix domain socket SSL does not work. <br />
</dl><br />
=== '''I'm using pgpool-II in replication mode. I expected that pgpool-II replaces current_timestamp call with time constants in my INSERT query, but actually it doesn't. Why?''' ===<br />
:Probably your INSERT query uses schema qualied table name (like public.mytable) and you did not install pool_regclass function coming pgpool. Without pgpool_reglclass, pgpool-II only deals with table names without schema qualification.<br />
<br />
=== '''Why max_connection must satisfy this formula max_connection >= (num_init_children * max_pool) and not max_connection >= num_init_children?''' ===<br />
: Probably you need to understand how pgpool uses these variables. Here is internal processing inside pgpool.<br />
<ol><br />
<li>Wait for connection request from clients.<br />
<li>pgpool child receives connection request from a client.<br />
<li>The pgpool child looks for existing connection in the pool which<br />
has requested database/user pair up to max_pool.<br />
<li>If found, reuse it.<br />
<li> If not found, opens a new connection to PostgreSQL and registers to<br />
the pool. If the pool has no empty slot, closes the oldest<br />
connection to PostgreSQL and reuse the slot.<br />
<li>Do some query processing until the client sends session close request.<br />
<li>Close the connection to client but keeps the connection to<br />
PostgreSQL for future use.<br />
<li>Go to #1<br />
</ol><br />
<br />
=== '''Is connection pool cache shared among pgpool process?''' ===<br />
:No, the connection pool cache is in pgpool's process private memory and is not shared by other pgpool. This is how the connection cache is managed: Suppose pgpool process 12345 has connection cache for database A/user B but process 12346 does not have connection cache for database A/user B and both 12345 and 12346 are in idle state(no client is connecting at this point). If client connects to pgpool process 12345 with database A/user B, then the exisiting connection of 12345 is reused. On the other hand, If client connects to pgpool process 12346, 12346 needs to create new connection. Whether 12345 or 12346 is chosen, is not under control of pgpool. However in the long run, each pgpool child process will be equally chosen and it is expected that each process's pool will be resued equally.<br />
<br />
=== '''Why my SELECTs are not cached?''' ===<br />
<br />
:Certain libraries such as iBatis, MyBatis always rollback transactions if they are not explicitely committed. Pgpool never caches SELECTs result in a rollbacked transaction because they might not be inconsistent.<br />
<br />
=== '''Can I use # comments or blank lines in pool_passwd?''' ===<br />
<br />
: The answer is simple. No (just like /etc/passwd).<br />
<br />
=== '''I cannot use MD5 authentication if start pgpool without -n option. Why?''' ===<br />
: You must have given -f option as a relative path: i.e. "-f pgpool.conf", rather than full path: i.e. "-f /usr/local/etc/pgpool.conf". Pgpool tries to locate the full path of pool_passwd (which is neccesary for MD5 auth) from pgpool.conf path. This is fine with -n option. However if pgpool starts without -n option, it changes current directory to "/", which is neccessary processs for daemonizing. As a result, pgpool tries to open "/pool_passwd", which will not successs.<br />
<br />
=== '''I see standby servers go down status in steaming replication mode and see PostgreSQL messages "terminating connection due to conflict" Why?''' ===<br />
: If you see following messages along with those, it is likely vacuum on primary server removes rows which SELECTs on standby server want to see. Workaround is setting "hot_standby_feedback = on" in your standby server's postgresql.conf.<br />
<br />
<dl><dd><pre><br />
2013-04-07 19:38:10 UTC FATAL: terminating connection due to conflict with recovery<br />
2013-04-07 19:38:10 UTC DETAIL: User query might have needed to see row versions that must be removed.<br />
2013-04-07 19:38:10 UTC HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />
2013-04-07 19:38:10 UTC LOG: could not send data to client: Connection reset by peer<br />
2013-04-07 19:38:10 UTC ERROR: canceling statement due to conflict with recovery<br />
2013-04-07 19:38:10 UTC DETAIL: User query might have needed to see row versions that must be removed.<br />
2013-04-07 19:38:10 UTC LOG: could not send data to client: Broken pipe<br />
2013-04-07 19:38:10 UTC FATAL: connection to client lost<br />
</pre></dl><br />
<br />
=== '''Every few minites load of the system which pgpool-II running on gets high as much as 5-10. Why?''' ===<br />
: Mulptiple users stats that this is observed only Linux kernel 3.0. 2.6 or 3.2 does show the behavior. We suspect that there is a problem with 3.0 kernel. See more discussions on "[pgpool-general: 1528] Mysterious Load Spikes".<br />
<br />
=== '''When watchdog enabled and the connection number reach the number of num_init_children, VIP switchover occurs. Why?''' ===<br />
<br />
:When the connection number reach the number of num_init_children, the watchdog will be failed because select 1 is failed, and then VIP will be transfer to another pgpool. Unfortunately, there are no way to discriminate normal client's connections from watchdog's connection. Larger num_init_children, wd_life_point and smaller wd_interval may prevent the problem somewhat. <br />
<br />
:The next major version, pgpool-II 3.3, will support a new monitoring method which uses UDP heartbeat packets instead of queries such like 'SELECT 1' to resolve the problem.<br />
<br />
=== '''Why do I need to install pgpool_regclass? ''' ===<br />
: If you are using PostgreSQL 8.0 or later, installing pgpool_regclass function on all PostgreSQL to be accessed by pgpool-II is strongly recommended, as it is used internally by pgpool-II. Without this, handling of duplicate table names in different schema might cause trouble (temporary tables aren't a problem).<br />
:Related FAQ is here http://www.pgpool.net/mediawiki/index.php?title=FAQ&action=submit#I.27m_using_pgpool-II_in_replication_mode._I_expected_that_pgpool-II_replaces_current_timestamp_call_with_time_constants_in_my_INSERT_query.2C_but_actually_it_doesn.27t._Why.3F<br />
: If you are using PostgreSQL 9.4.0 or later and pgpool-II 3.3.4 or later, 3.4.0 or later, you don't need to install pgpool_regclass since PostgreSQL 9.4 has built-in pgpool_regclass like function "to_regclass".<br />
<br />
=== '''md5 authentication does not work. Please help''' ===<br />
: There's an excellent summary of various check points to set up md5 authentication. Please take a look at it.<br />
: http://www.pgpool.net/pipermail/pgpool-general/2013-May/001773.html<br />
<br />
=== '''I'm running pgpool/PostgreSQL on Amazon AWS and occasionaly I get network errors. Why?''' ===<br />
: It's a known problem with AWS. We recommend to complain to the Amazon support.<br />
: pgpool-II 3.3.4, 3.2.9 or later mitigate the problem by changing timeout value for connect(actually select system call) from 1 second to 10 seconds.<br />
: Also pgpool-II 3.4 or later has a switch to control the timeout value.<br />
<br />
=== '''I cannot run pcp command on my Ubuntu box. Why?''' ===<br />
: pcp commands need libpcp.so. In Ubuntu it is included "libpgpool0" package.<br />
<br />
=== '''On line recovery failed. How can I debug this?''' ===<br />
: pcp_recovery_node executes recovery_1st_stage_command and/or recovery_2nd_stage_command depending on your configuration. Those scripts are supposed to be executed on the master PostgreSQL node (the first live node in replication mode or primary node in streaming replication mode). "BackendError" means there's something wrong in pgpool and/or PostgreSQL. To verify this, I recommend followings;<br />
<br />
<ol><br />
<li>start pgpool with debug option<br />
<li>execute pcp_recovery_node<br />
<li>examin pgpool log and master PostgreSQL log<br />
</ol><br />
<br />
=== ''' Watchdog doesn't start if not all "other" nodes are alive'''===<br />
: It's a feature. Watchdog's lifeheck will start after all of the pgpools has started. Until this, failover of the virtual IP never occurs.<br />
<br />
=== '''If I start transaction, pgool-II also starts a transaction on standby nodes. Why?'''===<br />
: This is necessary to deal with the case when JDBC driver wants to use cursors. Pgpool-II takes a liberty of distributing SELECTs to the standby node including cursor statements. Unfortunately cursor statements need to be executed in an explicit transaction.<br />
<br />
=== '''When I use schema qualified table names, pgpool-II does not invalidate on memory query cache and I got outdated data. Why?'''===<br />
: It seems you did not install "pgpool_regclass" function. Without the function, pgpool-II ignores the schema name pat of the schema qualified table name and the cache invalidation fails.<br />
<br />
=== '''I periodically get error message like "read_startup_packet: incorrect packet length". What does it mean?'''===<br />
: Monitoring tools including Zabbix and Nagios periodically sends a packet or ping to the port which pgoool is listening on. Unfortunately those packets do not have correct contents, and pgpool-II complains it. If you are not sure who is sending such a packet, you could turn on "log_connections" to know the source host and port info. If they are from such tools, you could stop the monitoring to avoid the problem or even better, change the monitoring method to send legal query, for example, "SELECT 1". <br />
<br />
=== '''I'm getting repeated errors like this every few minutes on Tomcat: "An I/O Error occurred while sending to the backend" Why?'''===<br />
: Tomcat creates persistent connections to pgpool. If you set client_idle_limit to non 0, pgpool disconnects the connection and next time when Tomcat tries to send something to pgpool it breaks with the error message.<br />
: One solution is set client_idle_limit to 0. However this will leave lots of idle connections.<br />
: Another solution provided by Lachezar Dobrev is:<br />
: You might solve that by adding a time-out on the Tomcat side. http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html<br />
: What you should set is (AFAIK):<br />
: minIdle (default is 10, set to 0)<br />
: timeBetweenEvictionRunsMillis (default 5000)<br />
: minEvictableIdleTimeMillis (default 60000)<br />
:This will try every 5 seconds and close any connections that were not used in the last 60 seconds. If you keep the sum of both numbers below the client time-out on the pgpool size connections should be closed at Tomcat side before they time-out on the pgpool side.<br />
: It is also beneficial to set the<br />
: testOnBorrow (default false, set to true)<br />
: validationQuery (default none, set to 'SELECT version();' no quotes)<br />
: This will help with connections should they expire while waiting, without supplying a disconnected connection to the application.<br />
<br />
=== '''When I check pg_stat_activity view, I see a query like "SELECT count(*) FROM pg_catalog.pg_class AS c WHERE c.oid = pgpool_regclass('pgbench_accounts') AND c.relpersistence = 'u'" in active state for very long time. Why?'''===<br />
: It's a limitation of pg_stat_activity. You can safely ignore it.<br />
: Pgpool-II issues queries like above for internal use to master node. When user query runs in extended protocol mode (sent from JDBC driver, for example), pgpool-II's query also runs in the mode. To make pg_stat_activity recognize the query finishes, pgpool-II needs to send a packet called "Sync", which unfortunately breaks user's query (more precisely, unnamed portal). Thus pgpool-II sends "Flush" packet instead but then pg_stat_activity does not recognize the end of the query.<br />
: Interesting thing is, if you enable log_duration, it logs the query finishes.<br />
<br />
=== '''Online recovery always fails after certain minutes. Why? ''' ===<br />
: It is possible that PostgreSQL statement_timeout kills the online recovery process. The process is executed as a SQL statement and if it's running too long, PostgreSQL sends signal 2 to the SQL and kills it. Varying by the size of the database, the online recovery process takes very long time. Make sure to disable statement_timeout or set it long enough time.<br />
<br />
=== '''Why "SET default_transaction_isolation TO DEFAULT" fails ? ''' ===<br />
<br />
<dl><dd><pre><br />
$ psql -h localhost -p 9999 -c 'SET default_transaction_isolation to DEFAULT;'<br />
ERROR: kind mismatch among backends. Possible last query was: "SET default_transaction_isolation to DEFAULT;" kind details are: 0[N: statement: SET default_transaction_isolation to DEFAULT;] 1[C]<br />
HINT: check data consistency among db nodes<br />
ERROR: kind mismatch among backends. Possible last query was: "SET default_transaction_isolation to DEFAULT;" kind details are: 0[N: statement: SET default_transaction_isolation to DEFAULT;] 1[C]<br />
HINT: check data consistency among db nodes<br />
connection to server was lost<br />
</pre></dl><br />
: Pgpool-II detects that node 0 returns "N" (a NOTICE message comes from PostgreSQL) while node 1 returns "C" (which means the command finished).<br />
: Though pgpool-II expects that both node 0 and 1 returns identical messages, actually they are not. So pgpool-II threw an error.<br />
: Probably certain log/message settings are different in node 0 and 1. Please check client_min_messages or something like that.<br />
: They should be identical.<br />
<br />
=== '''How does pgpool-II find the primary node?'''===<br />
: pgpool-II issues "pg_SELECT pg_is_in_recovery()" to each DB node. If it returns true, then the node is a standby node. If one of DB nodes returns false, then the node is the primary node and done.<br />
: Because it is possible that promoting node could return true for the SELECT, if no primary node is found and "search_primary_node_timeout" is greater than 0, pgpool-II sleeps 1 second and contines to issues the SELECT query to each DB node again until total sleep time exceeds search_primary_node_timeout.<br />
<br />
=== '''Can I use pg_cancel_backend()?'''===<br />
: Remember that pgpool-II manages multiple PostgreSQL servers. To use the function, you not only need to identify the backend pid but the backend server.<br />
: If the query is running on the primary server, you can call the function something like<br />
<br />
<dl><dd><pre><br />
/*NO LOAD BALANCE*/ SELECT pg_cancel_backend(pid)<br />
</pre><br />
</dl><br />
: SQL comment is to prevent the SELECT be load balanced to standby. Of course you could issue the SELECT against directly the primary server.<br />
: If the query is running on one of standby servers, you need to issue the SELECT against directly the standby server.<br />
<br />
=== '''Why my client is disconnected to pgpool-II when failover happens?'''===<br />
: pgpool-II consists of many process where each process corresponds to client session. When failover occurs, each process may iterate on a loop for each backend without knowing a backend goes down. This may result in incorrect processing, or segfault in the worst case. For this reason, when failover occurs, pgpool-II parent process interrupt child process using signal to let them exit. Note that switch over using pcp_detach node has same effect.<br />
<br />
=== '''Why am I getting "LOG: forked new pcp worker ..," and "LOG: PCP process with pid: xxxx exit with SUCCESS." messages in pgpool log?''' ===<br />
: Prior to pgpool-II 3.5, pgpool could only handle single PCP command at a time and all PCP commands were handled by a single PCP child process which lives throughout the lifespan of pgpool-II main process. In pgpool II 3.5 the restriction of single PCP command is removed and pgpool-II can now handle multiple simultaneous PCP commands. For every PCP command issued to pgpool a new PCP child process is forked and that process exits after execution of the PCP command is complete. So these log messages are perfectly normal and are generated whenever a new PCP worker process is created or completes execution for a PCP command.<br />
<br />
== pgpoolAdmin Frequently Asked Questions ==<br />
<br />
=== '''pgpoolAdmin does not show any node in pgpool status and node status. Why?''' ===<br />
: pgpoolAdmin uses PHP's PostgreSQL extention (pg_connect and pg_query etc.). Probably the extention does not work as expected. Please check apache error log. Also please check the FAQ item below.<br />
<br />
=== '''Why does node status in pgpoolAdmin show "down" status even if PostgreSQL is up and running?''' ===<br />
: pgpoolAdmin checks PostgreSQL status by connecting with user = "health_check_user" and database = template1. Thus you should allow pgpoolAdmin to access PostgreSQL with those user and database without password. You can check PostgreSQL log to verify this. If health_check_user does not exist, you will see something like:<br />
: <pre>20148 2011-07-06 16:41:59 JST FATAL: role "foo" does not exist</pre><br />
: If the user is protected by password, you will see:<br />
<dl><dd><pre>20220 2011-07-06 16:42:16 JST FATAL: password authentication failed for user "foo"<br />
20221 2011-07-06 16:42:16 JST LOG: could not receive data from client: Connection reset by peer<br />
20221 2011-07-06 16:42:16 JST LOG: unexpected EOF within message length word<br />
20246 2011-07-06 16:42:26 JST LOG: could not receive data from client: Connection reset by peer<br />
20246 2011-07-06 16:42:26 JST LOG: unexpected EOF within message length word</pre></dl></div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1287
pgpool-II 3.6 development
2016-02-26T07:46:19Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/2/26 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| -<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| -<br />
| -<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Start after PostgreSQL 9.6 beta released<br />
|-<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|-<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| <br />
|-<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/3/31<br />
| Tatsuo<br />
|<br />
|<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial along with sample of escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| <br />
|-<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| All the new platforms that we want to support and add to BF should be decided by this date.<br />
|-<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.6_development&diff=1286
pgpool-II 3.6 development
2016-02-26T07:44:53Z
<p>Usama: </p>
<hr />
<div>Last update: 2016/2/26 (gray items are done, yellow items are behind schedule)<br />
<br />
{| class="wikitable"<br />
! <br />
! ID<br />
! Registered/start Date<br />
! Target Date<br />
! Person in charge<br />
! Overview<br />
! Status<br />
|- style="background:silver"<br />
| 1<br />
| pgpool-general:3907<br />
| 2015/08/02<br />
| 2015/10/28<br />
| Usama<br />
| watchdog info<br />
| Done in [pgpool-general: 4452]<br />
|-<br />
| 2<br />
| pgpool-general:3923<br />
| 2015/08/06<br />
| -<br />
| Tatsuo<br />
| pgpool_status<br />
| needs discussion, postpone to 3.6<br />
|-<br />
| 3<br />
| pgpool-hackers:994<br />
| 2015/08/05<br />
| -<br />
| Tatsuo<br />
| connect to necessary DB nodes<br />
| proposal, feedback, postpone to 3.6<br />
|-<br />
| 4<br />
| pgpool:330<br />
| 2015/08/12<br />
| -<br />
| Ahsan, Tatsuo<br />
| mesuring pgpool-II overhead<br />
| in progress, Tatsuo will review the result, postpone to 3.6<br />
|-<br />
| 5<br />
| pgpool-hackers:1034<br />
| 2015/09/03<br />
| -<br />
| -<br />
| add new child if it goes down<br />
| need to assign, postpone to 3.6<br />
|-<br />
| 6<br />
| pgpool-general:4016<br />
| 2015/09/02<br />
| -<br />
| -<br />
| deal with pg_terminate_backend<br />
| need to assign or expecting patches from user, postpone to 3.6<br />
|-<br />
| 7<br />
| Import PostgreSQL 9.6 parser<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Start after PostgreSQL 9.6 beta released<br />
|-<br />
| 8<br />
| Add SET command<br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| Add set command to configure session level configuraiton pgpool paramaeters. Change the pgpool load balance parameter on the fly.<br />
|-style="background:silver"<br />
| 9-1<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/15<br />
| 2016/2/15<br />
| Usama<br />
| Tool set porting work time estimate<br />
| Estimating work hours to determine the shedule. He estimated as "3.5D".<br />
|- style="background:silver"<br />
| 9-2<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/16<br />
| 2016/2/19<br />
| Usama<br />
| Tool set porting<br />
| PostgreSQL docs trees are ported as well. Confirmed to be able to generate HTML files<br />
|-<br />
| 9-3<br />
| Convert the pgpool documentation to SGML<br />
| 2016/2/26<br />
| 2016/2/29<br />
| Tatsuo<br />
| Prune PostgreSQL's SGML files to prepare for creating pgpool-II docs<br />
|<br />
|-<br />
| 10<br />
| Make PCP set configuration command public <br />
| 2016/2/15<br />
| -<br />
| -<br />
| -<br />
| <br />
|-<br />
| 11<br />
| Keep current session alive in-case of failover<br />
| 2016/2/15<br />
| 2016/3/31<br />
| Tatsuo<br />
|<br />
|<br />
|- style="background:silver"<br />
| 12<br />
| Yet another stuck connection problem<br />
| 2016/2/19<br />
| 2016/2/23<br />
| Usama<br />
|<br />
| pgpool-general: 4457<br />
|-<br />
|-<br />
| 13<br />
| Tutorial and example escalation and de-escalation scripts for using pgpool-II watchdog on AWS<br />
| 2016/2/26<br />
| <br />
| Usama<br />
|<br />
| <br />
|-<br />
| 100<br />
| Platform freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| All the new platforms that we want to support and add to BF should be decided by this date.<br />
|-<br />
| 101<br />
| Feature requirement freeze<br />
| 2016/2/19<br />
| 2016/3/15<br />
| -<br />
| -<br />
| We need to ensure all the features that we intend to add to 3.6 are speced out by this date <br />
|-<br />
| 102<br />
| Feature Freeze<br />
| 2016/2/19<br />
| 2016/7/30<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 103<br />
| Code Freeze<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| 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.<br />
|-<br />
| 104<br />
| pgpool-II 3.6 beta1<br />
| 2016/2/19<br />
| 2016/8/31<br />
| -<br />
| -<br />
| First Beta<br />
|-<br />
| 105<br />
| pgpool-II 3.6 RC1<br />
| 2016/2/19<br />
| 2016/9/30<br />
| -<br />
| -<br />
| One month after beta1<br />
|-<br />
| 106<br />
| pgpool-II 3.6.0 official release<br />
| 2016/2/19<br />
| 2016/10/30<br />
| -<br />
| -<br />
|<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features&diff=1196
pgpool-II 3.5 features
2015-12-17T15:01:41Z
<p>Usama: </p>
<hr />
<div>== Introducing pgpool-II 3.5 new features ==<br />
<br />
pgpool-II 3.5 is enhanced in many areas as previous major releases of pgpool-II.<br />
However this time pgpool-II enhances the performance in some use cases and this kind of changes are pretty rare in the pgpool-II history.<br />
Let's discuss performance of extended query protocol first.<br />
<br />
== Improved performance in extended query protocol ==<br />
<br />
''Extended query protocol'' is used in many applications written in<br />
various languages and APIs including Java and JDBC. One of the benefit<br />
of it is, it allows to reuse query plans to save planning time. The<br />
other benefit is it could make queries more secure. The extended query<br />
protocol allows to use ''parameters'' for query. Without this,<br />
applications need to generate query string by themselves and may<br />
introduce famous ''SQL injection'' attack.<br />
<br />
Until pgpool-II 3.4, unfortunately it is not good at handling the<br />
extended query protocol. It is very slow when the extended query<br />
protocol is executed through pgpool-II.<br />
<br />
=== Why extended protocol is slow anyway? ===<br />
<br />
In the extended query protocol, queries are divided into several<br />
phases: ''Parse'', ''Bind'', ''Execute'' and ''Sync'' (there are more<br />
message types in the protocol. See PostgreSQL docs for more<br />
details). Parse message requests to create query plans. Bind message<br />
requests to attach parameters to the plan. Execute message requests to<br />
execute the query. Note that in each phase PostgreSQL does not<br />
respond the each result in the each phases. Rather, all of the<br />
responses are replied back to clients (including pgpool-II) at once.<br />
<br />
However, pgpool-II needs to synchronize backend responses for internal<br />
processing. This is done by issuing additional ''Flush'' message in<br />
the each protocol phase, which requests response from backend. Problem<br />
is, this generates significant amount of network traffic and cause<br />
slowness of query execution through pgpool-II.<br />
<br />
[[File:why-extended-protocol-is-so-slow.png|left|thumb|400px|Diagram to explain why extended protocol is slow]]<br />
<br />
=== Overcoming the slowness ===<br />
<br />
[[File:extended-protocol-graph-3.5.png|right|thumb|400px|TPS pgpool-II 3.5 vs. 3.4 in extended protocol]]<br />
<br />
Pgpool-II 3.5 overcomes the weakness in some cases. In streaming<br />
replication mode, because pgpool-II does not need to sync each<br />
backend, pgpool-II 3.5 does not issue flush messages. This was not an<br />
easy project because pgpool-II's architecure prerequisite that backend<br />
responds each time when extended protocol messages was sent. The hard<br />
work is rewarded by significant performance improvement. We conducted a bench marking test on two AWS EC2 instances (m4.large) running on Cent OS 6 with PostgreSQL 9.4 being installed.<br />
pgpool-II and pgbench run on a separate AWS EC2 instance (m4.large).<br />
Bench marking<br />
shows that pgpool-II 3.5 is 20% to 250% faster than 3.4.<br />
<br />
The performance of other mode (native replication mode and raw mode)<br />
remains same.<br />
<br />
== Overcoming the thundering herd problem ==<br />
<br />
Pgpool-II has a problem called ''the thundering herd problem''.<br />
<br />
[[File:thundering-herd-graph-3.5.png|left|thumb|400px|TPS pgpool-II 3.5 vs. 3.4]]<br />
<br />
What is the thundering herd problem anyway?<br />
<br />
The Wikipedia says: <br />
<br />
<blockquote>The thundering herd problem occurs when a large number of processes<br />
waiting for an event are awoken when that event occurs, but only one<br />
process is able to proceed at a time. After the processes wake up,<br />
they all demand the resource and a decision must be made as to which<br />
process can continue. After the decision is made, the remaining<br />
processes are put back to sleep, only to all wake up again to request<br />
access to the resource.</blockquote><br />
<br />
Pgpool-II forks off child process and wait for connection requests<br />
from clients. When a request arrives only one of them can accept the<br />
request. Other process just are awoken and sleep again. Pgpool-II 3.5<br />
allow only one process to accept the request by using semaphore and<br />
never let other process awoken except the process which had been<br />
waiting for the semaphore. This eliminates the thundering herd problem.<br />
To enable the functionality, you must turn on the new parameter<br />
''serialize_accept'' in pgpool.conf. Also ''child_life_time'' must be<br />
disabled (set to 0), which is due to an limitation of current<br />
implementation. Note that the method is most effective when<br />
''num_init_children'' is large and the number of concurrent clients is<br />
relatively small. In our test case, pgpool-II 3.5 is 40% to 150%<br />
faster than 3.4.<br />
<br />
The graph left shows how pgpool-II 3.5 putperforms 3.4. We set everything (pgpool-II, PostgreSQL and pgbench) on a laptop which has 16GB mem and 512 GB SSD, running Ubuntu 14.04.<br />
We start pgbench with -C option which repeats connect and disconnect to pgpool-II to simulate the thundering herd problem.<br />
Note that the blue line shows raw PostgreSQL TPS for comparison.<br />
pgbench repeatedly connects and disconnects to PostgreSQL, which results in poor performance.<br />
This shows why we need connection pooling.<br />
<br />
<br />
== Watchdog enhancements ==<br />
<br />
The watchdog is a sub process of pgpool-II, which provides high availability and automatic failover functionality between pgpool-II nodes. The watchdog process provides this functionality by monitoring two or more pgpool-II nodes and by promoting the standby node to master/active in case of a failure. The watchdog feature has been part of pgpool-II since version 3.2, and the pgpool-II 3.5 release has added some major enhancements to watchdog to make it more robust and resilient in handling failure scenarios.<br />
<br />
The enhancements also overcome most of the shortcoming and the problems of the existing watchdog features, the following shortcomings of the existing watchdog are addressed in pgpool-II 3.5:<br />
<br />
''• The watchdog now considers the quorum in the cluster. And only performs node escalation (acquire delegate-IP) when the quorum in the cluster is complete, This is how watchdog ensures that even in case of network partitioning or momentary split-brain the watchdog cluster keep working smoothly and the IP conflict situation should not happen, because of multiple not trying to acquire same virtual IP.<br />
<br />
• All pgpool-II nodes participating in the watchdog cluster make sure that the pgpool-II configuration of all nodes in the cluster is consistent so the user should not get any unwelcome surprise because of any configuration mistake at the time of node escalations.<br />
<br />
• Watchdog nodes now have configurable watchdog node priority (wd_priority), This will give the users more control on which node should become a leader node when the cluster elects the master node.<br />
<br />
• The third watchdog node health-checking (lifechecking), mode "external" along with already existing "query" and "heartbeat" is added to the watchdog. This new mode disables the internal lifecheck of pgpool-II watchdog and relies on external system to inform about node health status. Using this mode any external/3rd party node health checking system can be integrated with pgpool-II watchdog for lifechecking.<br />
<br />
• The new watchdog cluster always keeps exchanging the periodic beacon messages and keep looking for problems like split-brain syndrome and automatically recover from it.<br />
<br />
• Now user can provide scripts to be executed at time of escalation and de-escalation to master/leader nodes, This allows the pgpool-II watchdog to work on the different flavors of network (cloud platforms) where acquiring and releasing of virtual/elastic IP requires proprietary scripts/commands.''<br />
<br />
<br />
==PCP system overhauling==<br />
<br />
The whole PCP system, both server and client side get a major overhaul in pgpool-II 3.5. Apart from the code refactoring that significantly improves the manageability and maintanibility of the of PCP library and front-end clients, the overhauled PCP adds the following new features.<br />
<br />
• The PCP communication protocol is enhanced and now more detailed PostgreSQL style ERROR and DEBUG messages can be delivered from the PCP server to the front-ends, This change not only makes the message style of the PCP system more in line with the rest of pgpool-II but also helps in making the user experience of PCP more enhanced by providing the user with detailed error and debug information.<br />
<br />
• Traditionally the PCP server was single process and was able to only process one command at a time, After the overhauling pgpool-II PCP server can now handle multiple simultaneous PCP commands. The exception to this is pcp_recovery_node, Only one recovery command is allowed to run at one time.<br />
<br />
• PCP process now considers the shutdown modes. Previously pcp_child didn't not care about if the mode "smart or fast" was provided in the shutdown request issued to it by pgpool-II process and used to always kill it-self instantly. The PCP in pgpool-II 3.5 considers the shutdown mode and when the smart shutdown is requested, it makes sure that the current executing PCP command is finished before proceeding with the shutdown.<br />
<br />
• PCP front-end commands now support long command line options. In previous versions, each PCP command only accepts the fixed number of command line options and in a fixed order. Overhauling of the PCP system in pgpool-II 3.5 enables all the PCP utilities to accept long command line options in any order and user can also omit the arguments for which they want to use the default values. <br />
<br />
• Old command format<br />
<br />
pcp_attach_node _timeout_ _host_ _port_ _userid_ passed nodded <br />
<br />
• New Command format<br />
<br />
pcp_attach_node [options...] node_id<br />
<br />
<br />
• Your PCP password is now safe with pgpool-II 3.5. PCP utilities used to accept PCP password as a command line argument, which was a big security flaw. That password in the command line could easily be captured using the ps command. Now in the overhauled version of the PCP system all the utilities get the password from password prompt or can also read it from the .password file. PCP client side uses the PCPPASSFILE environment variable which can be used to provide the patch of the .password file.<br />
<br />
== Importing PostgreSQL 9.5 parser ==<br />
<br />
Pgpool-II has a built-in SQL parser which is used for mainly query<br />
dispatching and load balancing. The parser is being imported from<br />
PostgreSQL. Pgpool-II 3.4's SQL parser was imported from PostgreSQL<br />
9.4 and does not understand new syntax employed in PostgreSQL 9.5.<br />
Those queries the parser does not know are sent to the primary<br />
node and are never load balanced, which makes pgpool-II less effective<br />
when it needs to handle those queries.<br />
<br />
Pgpool-II 3.5 imports the SQL parser from PostgreSQL 9.5 and it can<br />
understand new syntax introduced in PostgreSQL 9.5. Especially<br />
''GROUPING SET'', ''CUBE'', ''ROLLUP'' and ''TABLESAMPLE'', now can be<br />
be load balanced and can be used in query cache. Of course pgpool-II<br />
3.5 understands PostgreSQL syntax used in 9.4 as well.<br />
<br />
Also ''INSERT...ON CONFLICT'' and ''UPDATE tab SET (col1, col2, ...) =<br />
(SELECT ...) ...'' can now be properly handled in query rewriting in<br />
native replication mode.<br />
<br />
== Other new features ==<br />
<br />
Some PassS systems including Heroku does not allow to use systems<br />
databases, i.e. postgres and template1. This prevent pgpool-II from<br />
using such that PassS. New parameters ''health_check_database'' and<br />
''sr_check_database'' allow to specify the database used for health<br />
checking and the database used for streaming replication delay<br />
respectively.<br />
<br />
''show pool_nodes'' which briefly describes the status of each backend now shows how many SELECTs are issued to them.<br />
So you can quickly recognize the effect of load balancing for example.<br />
<br />
test=# show pool_nodes;<br />
node_id | hostname | port | status | lb_weight | role | select_cnt <br />
---------+----------+-------+--------+-----------+---------+------------<br />
0 | /tmp | 11002 | 2 | 0.500000 | primary | 338230<br />
1 | /tmp | 11003 | 2 | 0.500000 | standby | 163939<br />
(2 rows)</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_features&diff=1195
pgpool-II 3.5 features
2015-12-17T13:28:08Z
<p>Usama: </p>
<hr />
<div>== Introducing pgpool-II 3.5 new features ==<br />
<br />
pgpool-II 3.5 is enhanced in many areas as previous major releases of pgpool-II.<br />
However this time pgpool-II enhances the performance in some use cases and this kind of changes are pretty rare in the pgpool-II history.<br />
Let's discuss performance of extended query protocol first.<br />
<br />
== Improved performance in extended query protocol ==<br />
<br />
''Extended query protocol'' is used in many applications written in<br />
various languages and APIs including Java and JDBC. One of the benefit<br />
of it is, it allows to reuse query plans to save planning time. The<br />
other benefit is it could make queries more secure. The extended query<br />
protocol allows to use ''parameters'' for query. Without this,<br />
applications need to generate query string by themselves and may<br />
introduce famous ''SQL injection'' attack.<br />
<br />
Until pgpool-II 3.4, unfortunately it is not good at handling the<br />
extended query protocol. It is very slow when the extended query<br />
protocol is executed through pgpool-II.<br />
<br />
=== Why extended protocol is slow anyway? ===<br />
<br />
In the extended query protocol, queries are divided into several<br />
phases: ''Parse'', ''Bind'', ''Execute'' and ''Sync'' (there are more<br />
message types in the protocol. See PostgreSQL docs for more<br />
details). Parse message requests to create query plans. Bind message<br />
requests to attach parameters to the plan. Execute message requests to<br />
execute the query. Note that in each phase PostgreSQL does not<br />
respond the each result in the each phases. Rather, all of the<br />
responses are replied back to clients (including pgpool-II) at once.<br />
<br />
However, pgpool-II needs to synchronize backend responses for internal<br />
processing. This is done by issuing additional ''Flush'' message in<br />
the each protocol phase, which requests response from backend. Problem<br />
is, this generates significant amount of network traffic and cause<br />
slowness of query execution through pgpool-II.<br />
<br />
[[File:why-extended-protocol-is-so-slow.png|left|thumb|400px|Diagram to explain why extended protocol is slow]]<br />
<br />
=== Overcoming the slowness ===<br />
<br />
[[File:extended-protocol-graph-3.5.png|right|thumb|400px|TPS pgpool-II 3.5 vs. 3.4 in extended protocol]]<br />
<br />
Pgpool-II 3.5 overcomes the weakness in some cases. In streaming<br />
replication mode, because pgpool-II does not need to sync each<br />
backend, pgpool-II 3.5 does not issue flush messages. This was not an<br />
easy project because pgpool-II's architecure prerequisite that backend<br />
responds each time when extended protocol messages was sent. The hard<br />
work is rewarded by significant performance improvement. We conducted a bench marking test on two AWS EC2 instances (m4.large) running on Cent OS 6 with PostgreSQL 9.4 being installed.<br />
pgpool-II and pgbench run on a separate AWS EC2 instance (m4.large).<br />
Bench marking<br />
shows that pgpool-II 3.5 is 20% to 250% faster than 3.4.<br />
<br />
The performance of other mode (native replication mode and raw mode)<br />
remains same.<br />
<br />
== Overcoming the thundering herd problem ==<br />
<br />
Pgpool-II has a problem called ''the thundering herd problem''.<br />
<br />
[[File:thundering-herd-graph-3.5.png|left|thumb|400px|TPS pgpool-II 3.5 vs. 3.4]]<br />
<br />
What is the thundering herd problem anyway?<br />
<br />
The Wikipedia says: <br />
<br />
<blockquote>The thundering herd problem occurs when a large number of processes<br />
waiting for an event are awoken when that event occurs, but only one<br />
process is able to proceed at a time. After the processes wake up,<br />
they all demand the resource and a decision must be made as to which<br />
process can continue. After the decision is made, the remaining<br />
processes are put back to sleep, only to all wake up again to request<br />
access to the resource.</blockquote><br />
<br />
Pgpool-II forks off child process and wait for connection requests<br />
from clients. When a request arrives only one of them can accept the<br />
request. Other process just are awoken and sleep again. Pgpool-II 3.5<br />
allow only one process to accept the request by using semaphore and<br />
never let other process awoken except the process which had been<br />
waiting for the semaphore. This eliminates the thundering herd problem.<br />
To enable the functionality, you must turn on the new parameter<br />
''serialize_accept'' in pgpool.conf. Also ''child_life_time'' must be<br />
disabled (set to 0), which is due to an limitation of current<br />
implementation. Note that the method is most effective when<br />
''num_init_children'' is large and the number of concurrent clients is<br />
relatively small. In our test case, pgpool-II 3.5 is 40% to 150%<br />
faster than 3.4.<br />
<br />
The graph left shows how pgpool-II 3.5 putperforms 3.4. We set everything (pgpool-II, PostgreSQL and pgbench) on a laptop which has 16GB mem and 512 GB SSD, running Ubuntu 14.04.<br />
We start pgbench with -C option which repeats connect and disconnect to pgpool-II to simulate the thundering herd problem.<br />
Note that the blue line shows raw PostgreSQL TPS for comparison.<br />
pgbench repeatedly connects and disconnects to PostgreSQL, which results in poor performance.<br />
This shows why we need connection pooling.<br />
<br />
== Importing PostgreSQL 9.5 parser ==<br />
<br />
Pgpool-II has a built-in SQL parser which is used for mainly query<br />
dispatching and load balancing. The parser is being imported from<br />
PostgreSQL. Pgpool-II 3.4's SQL parser was imported from PostgreSQL<br />
9.4 and does not understand new syntax employed in PostgreSQL 9.5.<br />
Those queries the parser does not know are sent to the primary<br />
node and are never load balanced, which makes pgpool-II less effective<br />
when it needs to handle those queries.<br />
<br />
Pgpool-II 3.5 imports the SQL parser from PostgreSQL 9.5 and it can<br />
understand new syntax introduced in PostgreSQL 9.5. Especially<br />
''GROUPING SET'', ''CUBE'', ''ROLLUP'' and ''TABLESAMPLE'', now can be<br />
be load balanced and can be used in query cache. Of course pgpool-II<br />
3.5 understands PostgreSQL syntax used in 9.4 as well.<br />
<br />
Also ''INSERT...ON CONFLICT'' and ''UPDATE tab SET (col1, col2, ...) =<br />
(SELECT ...) ...'' can now be properly handled in query rewriting in<br />
native replication mode.<br />
<br />
== Watchdog enhancements ==<br />
<br />
The watchdog is a sub process of pgpool-II, which provides high availability and automatic failover functionality between pgpool-II nodes. The watchdog process provides this functionality by monitoring two or more pgpool-II nodes and by promoting the standby node to master/active in case of a failure. The watchdog feature has been part of pgpool-II since version 3.2, and the pgpool-II 3.5 release has added some major enhancements to watchdog to make it more robust and resilient in handling failure scenarios.<br />
<br />
The enhancements also overcome most of the shortcoming and the problems of the existing watchdog features, the following shortcomings of the existing watchdog are addressed in pgpool-II 3.5:<br />
<br />
''-- The watchdog now considers the quorum in the cluster. And only performs node escalation (acquire delegate-IP) when the quorum in the cluster is complete, This is how watchdog ensures that even in case of network partitioning or momentary split-brain the watchdog cluster keep working smoothly and the IP conflict situation should not happen, because of multiple not trying to acquire same virtual IP.<br />
<br />
-- All pgpool-II nodes participating in the watchdog cluster make sure that the pgpool-II configuration of all nodes in the cluster is consistent so the user should not get any unwelcome surprise because of any configuration mistake at the time of node escalations.<br />
<br />
-- Watchdog nodes now have configurable watchdog node priority (wd_priority), This will give the users more control on which node should become a leader node when the cluster elects the master node.<br />
<br />
-- The third watchdog node health-checking (lifechecking), mode "external" along with already existing "query" and "heartbeat" is added to the watchdog. This new mode disables the internal lifecheck of pgpool-II watchdog and relies on external system to inform about node health status. Using this mode any external/3rd party node health checking system can be integrated with pgpool-II watchdog for lifechecking.<br />
<br />
-- The new watchdog cluster always keeps exchanging the periodic beacon messages and keep looking for problems like split-brain syndrome and automatically recover from it.<br />
<br />
-- Now user can provide scripts to be executed at time of escalation and de-escalation to master/leader nodes, This allows the pgpool-II watchdog to work on the different flavors of network (cloud platforms) where acquiring and releasing of virtual/elastic IP requires proprietary scripts/commands.''<br />
<br />
== Other new features ==<br />
<br />
Some PassS systems including Heroku does not allow to use systems<br />
databases, i.e. postgres and template1. This prevent pgpool-II from<br />
using such that PassS. New parameters ''health_check_database'' and<br />
''sr_check_database'' allow to specify the database used for health<br />
checking and the database used for streaming replication delay<br />
respectively.<br />
<br />
''show pool_nodes'' which briefly describes the status of each backend now shows how many SELECTs are issued to them.<br />
So you can quickly recognize the effect of load balancing for example.<br />
<br />
test=# show pool_nodes;<br />
node_id | hostname | port | status | lb_weight | role | select_cnt <br />
---------+----------+-------+--------+-----------+---------+------------<br />
0 | /tmp | 11002 | 2 | 0.500000 | primary | 338230<br />
1 | /tmp | 11003 | 2 | 0.500000 | standby | 163939<br />
(2 rows)</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_watchdog_test&diff=1079
pgpool-II 3.5 watchdog test
2015-11-02T09:40:09Z
<p>Usama: </p>
<hr />
<div>{|<br />
|Test Num<br />
|Category<br />
|Test Description<br />
|Expected Output<br />
|How to test<br />
|Assigned-to<br />
|----<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|1<br />
|Installation<br />
|Make sure that the new watchdog is installed and configured successfully <br />
|<br />
|<br />
|<br />
|----<br />
|2<br />
|Upgrade<br />
|Make sure that pgpool II with new watchdog can be installed on a system running pgpool II with the old watchdog<br />
|<br />
|<br />
|<br />
|----<br />
|3<br />
|Configuration<br />
|Make sure that pgpool II can be configured successfully with one primary and one stand-by configuration<br />
|<br />
|<br />
|<br />
|----<br />
|4<br />
|Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a sample query <br />
|Configruation<br />
|<br />
|<br />
|----<br />
|4.1<br />
|Functional testing<br />
|Shutdown Host-1's pgpool instanse and execute query again<br />
|Host-2 should take and respond to query<br />
|<br />
|<br />
|----<br />
|4.2<br />
|Functional testing<br />
|Shutdown Host-2's pgpool instanse and execute query again<br />
|Host-3 should take and respond to query<br />
|<br />
|<br />
|----<br />
|4.3<br />
|Functional testing<br />
|Start Host-1's pgpool instanse and execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|5<br />
|Failover scenarions / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a sample query <br />
|Configruation<br />
|<br />
|<br />
|----<br />
|5.1<br />
|Failover scenarios<br />
|Un-Plug Host-1's network cable and execute query again<br />
|Host-2 should take and respond to query<br />
|<br />
|<br />
|----<br />
|5.2<br />
|Failover scenarios<br />
|Un-Plug Host-2's network cable and execute query again<br />
|Host-3 should take and respond to query<br />
|<br />
|<br />
|----<br />
|5.3<br />
|Failover scenarios<br />
|Plug Host-1's network cable execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|6<br />
|Functional testing / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a long query <br />
|<br />
|<br />
|<br />
|----<br />
|6.1<br />
|Functional testing<br />
|Shutdown / Power Off Host-1's instanse and execute query again<br />
|Host-2 should take over and start responding, need to see the already running query response. <br />
|<br />
|<br />
|----<br />
|6.2<br />
|Functional testing<br />
|Shutdown / Power Off Host-2's instanse and execute query again<br />
|Host-3 should take over and start responding, need to see the already running query response. <br />
|<br />
|<br />
|----<br />
|6.3<br />
|Functional testing<br />
|Start Host-1's pgpool instanse and execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|7.1<br />
|Cheking other functionality of watchdog <br />
|Changing active/standby state in case of certain faults detected<br />
|<br />
|<br />
|<br />
|----<br />
|7.2<br />
|Cheking other functionality of watchdog <br />
|Automatic virtual IP address assigning synchronous to server switching<br />
|<br />
|<br />
|<br />
|----<br />
|7.3<br />
|Cheking other functionality of watchdog <br />
|Automatic registration of a server as standby in recovery<br />
|<br />
|<br />
|<br />
|----<br />
|8<br />
|Isolated master scenario / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a query<br />
|<br />
|<br />
|<br />
|----<br />
|8.1<br />
|Isolated master scenario<br />
|Break the connectivity between pgpool watchdog primary and stand node by bringing down connectivity on the stand-by.<br />
|Split brain testing ensures that their is only one master at a time that the clients can connect to. The stand-by should be promoted as the primary and the clients shouldn't be able to connect to the old master.<br />
|<br />
|<br />
|----<br />
|9<br />
|Networking Isolation scenarion<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|9.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10<br />
|Database Failure<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10.2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11<br />
|Watchdog agent failure<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11.2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|12<br />
|Pgpool-II Watchdog integration<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|12.1<br />
|PG backend failover with watchdog<br />
|Test the command interlocking, when pgpool-II watchdog in enabled.<br />
|The failover and follow master scripts should only be executed by one pgpool-II node<br />
|<br />
|<br />
|----<br />
|12.2<br />
|PG backend failback with watchdog<br />
|Test the command interlocking, when pgpool-II watchdog in enabled.<br />
|The failback scripts should only be executed by one pgpool-II node<br />
|<br />
|<br />
|----<br />
|12.3<br />
|online recovery with watchdog enabled<br />
|Execute online recovery with watchdog enabled.<br />
|<br />
|<br />
|<br />
|----<br />
|12.4<br />
|pgpool-II configuration integrity <br />
|Perform test with changing pgpool-II configurations on different pgpool-II nodes<br />
|Standby watchdog shoud report and fail to start if the configurations on master node is differnet from this node<br />
|<br />
|<br />
|----<br />
|13<br />
|integrate external node health checking <br />
|Test if watchdog can successfully integrate with external health-checking system<br />
|send the node down and node alive messages to watchdog ipc socket and it should handle these appropriately<br />
|<br />
|<br />
|----<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=pgpool-II_3.5_watchdog_test&diff=1078
pgpool-II 3.5 watchdog test
2015-11-02T09:36:50Z
<p>Usama: </p>
<hr />
<div>{|<br />
|Test Num<br />
|Category<br />
|Test Description<br />
|Expected Output<br />
|How to test<br />
|Assigned-to<br />
|----<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|1<br />
|Installation<br />
|Make sure that the new watchdog is installed and configured successfully <br />
|<br />
|<br />
|<br />
|----<br />
|2<br />
|Upgrade<br />
|Make sure that pgpool II with new watchdog can be installed on a system running pgpool II with the old watchdog<br />
|<br />
|<br />
|<br />
|----<br />
|3<br />
|Configuration<br />
|Make sure that pgpool II can be configured successfully with one primary and one stand-by configuration<br />
|<br />
|<br />
|<br />
|----<br />
|4<br />
|Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a sample query <br />
|Configruation<br />
|<br />
|<br />
|----<br />
|4.1<br />
|Functional testing<br />
|Shutdown Host-1's pgpool instanse and execute query again<br />
|Host-2 should take and respond to query<br />
|<br />
|<br />
|----<br />
|4.2<br />
|Functional testing<br />
|Shutdown Host-2's pgpool instanse and execute query again<br />
|Host-3 should take and respond to query<br />
|<br />
|<br />
|----<br />
|4.3<br />
|Functional testing<br />
|Start Host-1's pgpool instanse and execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|5<br />
|Failover scenarions / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a sample query <br />
|Configruation<br />
|<br />
|<br />
|----<br />
|5.1<br />
|Failover scenarios<br />
|Un-Plug Host-1's network cable and execute query again<br />
|Host-2 should take and respond to query<br />
|<br />
|<br />
|----<br />
|5.2<br />
|Failover scenarios<br />
|Un-Plug Host-2's network cable and execute query again<br />
|Host-3 should take and respond to query<br />
|<br />
|<br />
|----<br />
|5.3<br />
|Failover scenarios<br />
|Plug Host-1's network cable execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|6<br />
|Functional testing / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a long query <br />
|<br />
|<br />
|<br />
|----<br />
|6.1<br />
|Functional testing<br />
|Shutdown / Power Off Host-1's instanse and execute query again<br />
|Host-2 should take over and start responding, need to see the already running query response. <br />
|<br />
|<br />
|----<br />
|6.2<br />
|Functional testing<br />
|Shutdown / Power Off Host-2's instanse and execute query again<br />
|Host-3 should take over and start responding, need to see the already running query response. <br />
|<br />
|<br />
|----<br />
|6.3<br />
|Functional testing<br />
|Start Host-1's pgpool instanse and execute query again<br />
|Need to see which host will respond to query<br />
|<br />
|<br />
|----<br />
|7.1<br />
|Cheking other functionality of watchdog <br />
|Changing active/standby state in case of certain faults detected<br />
|<br />
|<br />
|<br />
|----<br />
|7.2<br />
|Cheking other functionality of watchdog <br />
|Automatic virtual IP address assigning synchronous to server switching<br />
|<br />
|<br />
|<br />
|----<br />
|7.3<br />
|Cheking other functionality of watchdog <br />
|Automatic registration of a server as standby in recovery<br />
|<br />
|<br />
|<br />
|----<br />
|8<br />
|Isolated master scenario / Setup<br />
|Three pgpool instanses (Host-1, Host-2, Host-3) are running on different machine using Ubutu 13:04. Connect to Host-1 and execute a query<br />
|<br />
|<br />
|<br />
|----<br />
|8.1<br />
|Isolated master scenario<br />
|Break the connectivity between pgpool watchdog primary and stand node by bringing down connectivity on the stand-by.<br />
|Split brain testing ensures that their is only one master at a time that the clients can connect to. The stand-by should be promoted as the primary and the clients shouldn't be able to connect to the old master.<br />
|<br />
|<br />
|----<br />
|9<br />
|Networking Isolation scenarion<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|9.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10<br />
|Database Failure<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|10.2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11<br />
|Watchdog agent failure<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11.1<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|11.2<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|12<br />
|Pgpool-II Watchdog integration<br />
|<br />
|<br />
|<br />
|<br />
|----<br />
|12.1<br />
|PG backend failover with watchdog<br />
|Test the command interlocking, when pgpool-II watchdog in enabled.<br />
|The failover and follow master scripts should only be executed by one pgpool-II node<br />
|<br />
|<br />
|----<br />
|12.2<br />
|PG backend failback with watchdog<br />
|Test the command interlocking, when pgpool-II watchdog in enabled.<br />
|The failback scripts should only be executed by one pgpool-II node<br />
|<br />
|<br />
|----<br />
|12.3<br />
|online recovery with watchdog enabled<br />
|Execute online recovery with watchdog enabled.<br />
|<br />
|<br />
|<br />
|----<br />
|12.4<br />
|pgpool-II configuration integrity <br />
|Perfom test with changing pgpool-II configurations on different pgpool-II nodes<br />
|standby watchdog shoud report and fail to start if the configurations on master node is differnet from this node<br />
|<br />
|<br />
|----<br />
|}</div>
Usama
https://pgpool.net/mediawiki/index.php?title=Source_code_repository&diff=1038
Source code repository
2015-07-06T08:49:39Z
<p>Usama: /* pgpool-II version policy */</p>
<hr />
<div>Pgpool source code repository is managed by [http://git.postgresql.org/gitweb PostgreSQL's git repository].<br />
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=summary pgpool-II git repository]<br />
* [http://git.postgresql.org/gitweb/?p=pgpooladmin.git;a=summary pgpoolAdmin git repository]<br />
* [http://git.postgresql.org/gitweb/?p=pgpoolha.git;a=summary pgpool-HA git repository]<br />
* [http://git.postgresql.org/gitweb/?p=pgpool1.git;a=summary pgpool-I git repository] (legacy version of pgpool. Not maintained anymore)<br />
<br />
== About pgpool-II source code management ==<br />
<br />
=== pgpool-II version policy ===<br />
We release "major version" each year, which is mostly backward compatible with the previous release, Exceptions to this rule are listed in the release notes when sometimes some existing feature is dropped, depreciated or a change that brings certain incompatibilities with the older versions. The versions are numbered in the form of A.B.C where A.B is the major version number while C represents the minor version of a release. Currently pgpool-II versions are represented by A == 3 i.e 3.B.C where 3.B represents the major version number, So current releases of pgpool-II is also sometimes referred as "3. X series".<br />
<br />
To absolutely identify version number, specifying the "minor version number (part C of A.B.C version string)" is important. This minor version is incremented for the bug fix release, which is roughly released every month. For example pgpool-II 3.5.0 represents the first release of pgpool-II 3.5 series and 3.5.1 is the second minor (bug fix) release of the same. Unlike major versions the new minor release is guaranteed to be 100% backward compatible with the previous minor release.<br />
<br />
=== pgpool-II branch policy ===<br />
<br />
pgpool-II source code is managed by git and hosted at [http://git.postgresql.org/gitweb PostgreSQL's git repository].<br />
Currently we have several branches to track each development tree. The under development branch (the candidate for next major version) is [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=summary master branch].<br />
<br />
Each time new major version is released, we create a branch to maintain the previous major version. We call them as "stable branches". Currently we have following stable branches.<br />
<br />
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_4_STABLE 3.4-stable]<br />
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_3_STABLE 3.3-stable]<br />
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_2_STABLE 3.2-stable]<br />
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_1_STABLE 3.1-stable]<br />
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_0_STABLE 3.0-stable]</div>
Usama
https://pgpool.net/mediawiki/index.php?title=TODO&diff=1019
TODO
2015-06-15T19:25:11Z
<p>Usama: /* Watchdog feature enhancement */</p>
<hr />
<div>__FORCETOC__<br />
<br />
== Pgpool-II TODO list ==<br />
<br />
=== Enhance performance of extended protocol case ===<br />
: When extended protocl (i.e. JDBC etc.) used, pgpool-II's overhead is pretty large compared with simple query. Need to enhance it.<br />
<br />
=== Automatically reattach a node in streaming master/slave configuration ===<br />
:In streaming master/slave configuration there could be an option to automatically reattach a node if it's up-to-date with the master (0 bytes behind). It often happens that due to minor network outage a slave node is dropped off from pgpool and stays down even if the the node has resumed replication with master and is up-to-date.pgpool already knows how much slave is behind master so i guess this wouldn't be too difficult to implement? (from bugtrack #17)<br />
<br />
=== Allow to use client encoding ===<br />
:It would be nice if pgpool client could use encoding which different from PostgreSQL server encoding.<br />
: To implement this, the parser should be able to handle "unsafe" encodings such as Shift_JIS. psql replaces second byte of each multibyte character to fool the parser. We could hire similar strategy.<br />
<br />
=== Send read query only to standbys even after fail over ===<br />
: We can configure pgpool-II to not send read queries to the primary. However after a fail over, the role of the node could be changed.<br />
: To solve the problem, we need new flag to specify that read queries always are sent to standbys regardless the fail over ([pgpool-general: 1621] backend weight after failover).<br />
<br />
=== Recognize multi statemnet queries ===<br />
: As stated in the document, pgpool-II does not recognize multi statement queries correctly (BEGIN;SELECT 1;END). Pgpool-II only parses the first element of the query ("BEGIN" in this case) and decides how to behave.<br />
: Of course this will bring various problems. It would be nice if pgpool-II could understand the each part of the multi statement queries.<br />
: Problem is, how PostgreSQL backend handles the multi statement queries. For example, when client sends BEGIN;SELECT 1;END, backend returns "Command Complete" respectively and "Ready for query" is returned only once. Thus, trying to split multi statement queries to non multi statement queries like what psql is doing will not work.<br />
<br />
=== Cursor statements are not load balanced, sent to all DB nodes in replication mode ===<br />
: DECLARE..FETCH are sent to all DB nodes in replication mode. This is because the SELECT might come with FOR UPDATE/FOR SHARE.<br />
: It would be nice if pgpool-II checks if the SELECT uses FOR UPDATE/FOR SHARE and if not, enable load balance (or only sends to the master node if load balance is disabled).<br />
: Note that some applications including psql could use CURSOR for SELECT. For example, from PostgreSQL 8.2, if "\set FETCH_COUNT n" is executed, psql unconditionaly uses a curor named "_psql_cursor".<br />
<br />
=== Support IPv6 network ===<br />
: As of 3.4, it is allowed to use IPv6 address for PostgreSQL backend server and bind address of pgpool-II itself.<br />
: However, PCP process still only binds to IPv4 and UNIX domain socket.<br />
<br />
=== Handle abnormal down of virtual IP interface when watchdog enabled ===<br />
: When virtual IP interface is dropped abnormally by manual ifconfig etc., there are no one holding VIP, and clients aren't able to connect pgpool-II. Watchdog of active pgpool should monitor the interface or VIP, and handle its down.<br />
<br />
=== Do not invalidate query cache created in a transaction in some cases ===<br />
: Currently new query cache for table t1 created in a transaction is removed at commit if there's DMLs which touch t1 in the same transaction. Apparently this is overkill for same cases:<br />
BEGIN;<br />
INSERT INTO t1 VALUES(1);<br />
SELECT * FROM t1;<br />
COMMIT;<br />
: To enhance this, we need to teach pgpool-II about "order of SELECTs and DMLs.".<br />
<br />
=== Fix memory leak in pool_config.c ===<br />
: The module in charge of parsing pgpool.conf has memory leak problem. Usually pgpool reads pgpool.conf just once at the start up time, it is not a big problem. However reloading pgpool.conf will leak memory and definitely a problem. Also using memory leak check tools like valgrind emit lots of error messages and very annoying. So it would be nice to fix the problem in the future.<br />
<br />
=== Add SET commnad ===<br />
: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.<br />
<br />
=== Put together a definition of error codes into a single header file ===<br />
: Currently most error codes used by pool_send_{error,fatal}_message() etc (e.g. "XX000", "XX001", "57000") are hard-coded in different sources. They should be defined as constants in a single header together.<br />
<br />
=== Create separate process for health checking ===<br />
: To make main process more stable, it would be better to make separate process which is responsible for health checking.<br />
<br />
=== Import PostgreSQL's latch module ===<br />
: Pgpool already has similar module but PostgreSQL's one seems more sophiscated and reliable.<br />
<br />
=== Import PostgreSQL 9.5's parser ===<br />
: No need to say for this.<br />
<br />
=== Allow to use schema qualifications in black_function_list and white_function_list ===<br />
: Currently schema qualifications are silently ignored in these parameter.<br />
<br />
=== Watchdog feature enhancement ===<br />
Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture.<br />
See the design proposal for watchdog enhancement [[http://pgpool.net/mediawiki/index.php/watchdog_feature_enhancement here]]<br />
<br />
== TODOs already done ==<br />
<br />
=== Allow to specify which node is dead when starting up ===<br />
: If we set longer health check timeout and/or many health check retries, starting up pgpool-II will take long time if some of DB nodes have been down because of health checking and retries in creating connection to backend.<br />
: pgpool_status should help here but for the very first starting up, we cannot use it.<br />
: It would be nice if we could tell pgpool-II about down node info.<br />
: As of 3.4, pgpool_status file is changed to a plain ASCII file and users could specify down node by using ordinary text editors.<br />
<br />
=== Ability to load balance based on Client IP, database, table etc. ===<br />
: From bugid 26: I have recently moved a database from Mysql to postgresql 9.1.5 which is behind a pgpool-II-3.1.4 . Everything went fine until i observed that some "tickets" are not created correctly by the application (OTRS) that populate the database.<br />
: After some debugging i found/guess that the problem is the following:<br />
: when a cron job wants to create a ticket he has to insert info in abut 10 tables, and i guess that the 2-nd, 3-rd ... inserts depends on the first. The problem was that this operation is not performed transactionally so after the first insert, when the app tries to perform the other inserts, first tries to select "the first insert", but this first insert is still not propagated to all nodes, and the error occurs.<br />
: I`m aware of the fact that if this entire operation would be performed transactionally (only on master) the issue is solved, but unfortunately i cannot modify the app.<br />
: So i want to know if there is any way that i can tell to pgpool something like :<br />
: any request from this ip do not load balance.<br />
<br />
: PS. temporary i have set the weight factor to 0 to the 2-nd and 3-rd postgresql slaves and it behaves ok, because reads and writes only from master.<br />
<br />
: P.P.S. there's also different request regarding load balance.<br />
: http://www.pgpool.net/pipermail/pgpool-general/2014-June/003032.html<br />
<br />
: This item has been implemented in 3.4 as "database_redirect_preference_list" and "app_name_redirect_preference_list".<br />
<br />
=== Import PostgreSQL's execption handling ===<br />
: PostgreSQL's exception handling (elog family) is pretty good tool to make codes to be simple and robust. It would be nice if pgpool could use this. This has been already done in 3.4.<br />
=== Allow to print user name in the logging ===<br />
: This will be useful for audit purpose. (done and will appear in pgpool-II-3.4.0).<br />
<br />
=== Remove on disk query cache ===<br />
: Old on disk query cache has almost 0 user and has sevior limitation, including no automatic cache invalidation. This has been already obsoleted since on memory query cache implemented. We should remove this (this has been already in git master and will appear in 3.4.0).<br />
<br />
=== Restart watchdog process when it abnormaly exits ===<br />
: It would be nice for pgpool main to restart watchdog process when it dies abormaly.<br />
<br />
=== Synchronize backend nodes information with watchdog when standby pgpool starts up ===<br />
: For example, when a certain node is detached from active pgpool and then standby pgpool starts up, the standby pgpool can't recognized that the node is detached. Standby pgpool should get information about node information from other pgpool.<br />
<br />
=== Avoid multiple pgpools from executing failover.sh simultaneously. ===<br />
: In master-slave mode with watchdog, when a backend DB is down, all pgpools execute failover.sh. It might cause something wrong.<br />
<br />
=== Add new parameter for searching primary node timeout ===<br />
: pgpool-II uses "recovery_timeout" for searching the primary node timeout after failover. Since this is an abuse of the parameter, we should add new parameter for searching the primary node.<br />
<br />
=== Allow to load balance even in an explicit transaction in replication mode ===<br />
: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.<br />
<br />
=== Add testing framework ===<br />
: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.<br />
<br />
=== Add switch to control select(2) time out in connecting to PostgreSQL ===<br />
: In connect_inet_domain_socket_by_port(), select(2) is issued to watch events on the fd created by non blocking connect(2). The time out parameter of select(2) is fixed to 1 second, which is not long enough in flakey network environment like AWS (http://www.pgpool.net/pipermail/pgpool-general/2014-May/002880.html).<br />
: To solve the problem, new switch to control the time out is desired (done for pgpool-II 3.4.0).<br />
<br />
=== Allow to specify which node is dead when starting up ===<br />
: If we set longer health check timeout and/or many health check retries, starting up pgpool-II will take long time if some of DB nodes have been down because of health checking and retries in creating connection to backend.<br />
: pgpool_status should help here but for the very first starting up, we cannot use it.<br />
: It would be nice if we could tell pgpool-II about down node info (pgpool-II 3.4.0 chages the pgpool_status format to ASCII. Thus users can edit the file if needed).<br />
<br />
=== Remove parallel query ===<br />
: Parallel query has severe restrictions such as certain queries cannot be used, nor in extended protocol (i.e. JDBC).<br />
: Also it is pain to upgrade to newer version of PostgreSQL's SQL parser (yes, pgpool-II uses PostgreSQL's parser code). In short, parallel query gives us small gain comparing with the work needed to maintain/enhance. So I would like to obsolete parallel query in the future pgpool-II release. (related parameters have been removed from pgpool.conf in 3.4.0. pgpool-II 3.5.0 will remove actual code).<br />
<br />
=== Enhance pcp commands ===<br />
: There are number of drawbacks in pcp commands including 1)the timeout parameter is not used any more and should be removed 2)error codes returned from the commands are completely useless 3)multiple commands can not be accepted simultaneously.<br />
: This has been already done in 3.5.</div>
Usama
https://pgpool.net/mediawiki/index.php?title=TODO&diff=1018
TODO
2015-06-15T19:20:59Z
<p>Usama: /* Import PostgreSQL's execption handling */</p>
<hr />
<div>__FORCETOC__<br />
<br />
== Pgpool-II TODO list ==<br />
<br />
=== Enhance performance of extended protocol case ===<br />
: When extended protocl (i.e. JDBC etc.) used, pgpool-II's overhead is pretty large compared with simple query. Need to enhance it.<br />
<br />
=== Automatically reattach a node in streaming master/slave configuration ===<br />
:In streaming master/slave configuration there could be an option to automatically reattach a node if it's up-to-date with the master (0 bytes behind). It often happens that due to minor network outage a slave node is dropped off from pgpool and stays down even if the the node has resumed replication with master and is up-to-date.pgpool already knows how much slave is behind master so i guess this wouldn't be too difficult to implement? (from bugtrack #17)<br />
<br />
=== Allow to use client encoding ===<br />
:It would be nice if pgpool client could use encoding which different from PostgreSQL server encoding.<br />
: To implement this, the parser should be able to handle "unsafe" encodings such as Shift_JIS. psql replaces second byte of each multibyte character to fool the parser. We could hire similar strategy.<br />
<br />
=== Send read query only to standbys even after fail over ===<br />
: We can configure pgpool-II to not send read queries to the primary. However after a fail over, the role of the node could be changed.<br />
: To solve the problem, we need new flag to specify that read queries always are sent to standbys regardless the fail over ([pgpool-general: 1621] backend weight after failover).<br />
<br />
=== Recognize multi statemnet queries ===<br />
: As stated in the document, pgpool-II does not recognize multi statement queries correctly (BEGIN;SELECT 1;END). Pgpool-II only parses the first element of the query ("BEGIN" in this case) and decides how to behave.<br />
: Of course this will bring various problems. It would be nice if pgpool-II could understand the each part of the multi statement queries.<br />
: Problem is, how PostgreSQL backend handles the multi statement queries. For example, when client sends BEGIN;SELECT 1;END, backend returns "Command Complete" respectively and "Ready for query" is returned only once. Thus, trying to split multi statement queries to non multi statement queries like what psql is doing will not work.<br />
<br />
=== Cursor statements are not load balanced, sent to all DB nodes in replication mode ===<br />
: DECLARE..FETCH are sent to all DB nodes in replication mode. This is because the SELECT might come with FOR UPDATE/FOR SHARE.<br />
: It would be nice if pgpool-II checks if the SELECT uses FOR UPDATE/FOR SHARE and if not, enable load balance (or only sends to the master node if load balance is disabled).<br />
: Note that some applications including psql could use CURSOR for SELECT. For example, from PostgreSQL 8.2, if "\set FETCH_COUNT n" is executed, psql unconditionaly uses a curor named "_psql_cursor".<br />
<br />
=== Support IPv6 network ===<br />
: As of 3.4, it is allowed to use IPv6 address for PostgreSQL backend server and bind address of pgpool-II itself.<br />
: However, PCP process still only binds to IPv4 and UNIX domain socket.<br />
<br />
=== Handle abnormal down of virtual IP interface when watchdog enabled ===<br />
: When virtual IP interface is dropped abnormally by manual ifconfig etc., there are no one holding VIP, and clients aren't able to connect pgpool-II. Watchdog of active pgpool should monitor the interface or VIP, and handle its down.<br />
<br />
=== Do not invalidate query cache created in a transaction in some cases ===<br />
: Currently new query cache for table t1 created in a transaction is removed at commit if there's DMLs which touch t1 in the same transaction. Apparently this is overkill for same cases:<br />
BEGIN;<br />
INSERT INTO t1 VALUES(1);<br />
SELECT * FROM t1;<br />
COMMIT;<br />
: To enhance this, we need to teach pgpool-II about "order of SELECTs and DMLs.".<br />
<br />
=== Fix memory leak in pool_config.c ===<br />
: The module in charge of parsing pgpool.conf has memory leak problem. Usually pgpool reads pgpool.conf just once at the start up time, it is not a big problem. However reloading pgpool.conf will leak memory and definitely a problem. Also using memory leak check tools like valgrind emit lots of error messages and very annoying. So it would be nice to fix the problem in the future.<br />
<br />
=== Add SET commnad ===<br />
: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.<br />
<br />
=== Put together a definition of error codes into a single header file ===<br />
: Currently most error codes used by pool_send_{error,fatal}_message() etc (e.g. "XX000", "XX001", "57000") are hard-coded in different sources. They should be defined as constants in a single header together.<br />
<br />
=== Create separate process for health checking ===<br />
: To make main process more stable, it would be better to make separate process which is responsible for health checking.<br />
<br />
=== Import PostgreSQL's latch module ===<br />
: Pgpool already has similar module but PostgreSQL's one seems more sophiscated and reliable.<br />
<br />
=== Import PostgreSQL 9.5's parser ===<br />
: No need to say for this.<br />
<br />
=== Allow to use schema qualifications in black_function_list and white_function_list ===<br />
: Currently schema qualifications are silently ignored in these parameter.<br />
<br />
=== Watchdog feature enhancement ===<br />
Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture.<br />
See the design proposal for watchdog enhancement [[http://pgpool.net/mediawiki/index.php/watchdog_feature_enhancement]]<br />
<br />
== TODOs already done ==<br />
<br />
=== Allow to specify which node is dead when starting up ===<br />
: If we set longer health check timeout and/or many health check retries, starting up pgpool-II will take long time if some of DB nodes have been down because of health checking and retries in creating connection to backend.<br />
: pgpool_status should help here but for the very first starting up, we cannot use it.<br />
: It would be nice if we could tell pgpool-II about down node info.<br />
: As of 3.4, pgpool_status file is changed to a plain ASCII file and users could specify down node by using ordinary text editors.<br />
<br />
=== Ability to load balance based on Client IP, database, table etc. ===<br />
: From bugid 26: I have recently moved a database from Mysql to postgresql 9.1.5 which is behind a pgpool-II-3.1.4 . Everything went fine until i observed that some "tickets" are not created correctly by the application (OTRS) that populate the database.<br />
: After some debugging i found/guess that the problem is the following:<br />
: when a cron job wants to create a ticket he has to insert info in abut 10 tables, and i guess that the 2-nd, 3-rd ... inserts depends on the first. The problem was that this operation is not performed transactionally so after the first insert, when the app tries to perform the other inserts, first tries to select "the first insert", but this first insert is still not propagated to all nodes, and the error occurs.<br />
: I`m aware of the fact that if this entire operation would be performed transactionally (only on master) the issue is solved, but unfortunately i cannot modify the app.<br />
: So i want to know if there is any way that i can tell to pgpool something like :<br />
: any request from this ip do not load balance.<br />
<br />
: PS. temporary i have set the weight factor to 0 to the 2-nd and 3-rd postgresql slaves and it behaves ok, because reads and writes only from master.<br />
<br />
: P.P.S. there's also different request regarding load balance.<br />
: http://www.pgpool.net/pipermail/pgpool-general/2014-June/003032.html<br />
<br />
: This item has been implemented in 3.4 as "database_redirect_preference_list" and "app_name_redirect_preference_list".<br />
<br />
=== Import PostgreSQL's execption handling ===<br />
: PostgreSQL's exception handling (elog family) is pretty good tool to make codes to be simple and robust. It would be nice if pgpool could use this. This has been already done in 3.4.<br />
=== Allow to print user name in the logging ===<br />
: This will be useful for audit purpose. (done and will appear in pgpool-II-3.4.0).<br />
<br />
=== Remove on disk query cache ===<br />
: Old on disk query cache has almost 0 user and has sevior limitation, including no automatic cache invalidation. This has been already obsoleted since on memory query cache implemented. We should remove this (this has been already in git master and will appear in 3.4.0).<br />
<br />
=== Restart watchdog process when it abnormaly exits ===<br />
: It would be nice for pgpool main to restart watchdog process when it dies abormaly.<br />
<br />
=== Synchronize backend nodes information with watchdog when standby pgpool starts up ===<br />
: For example, when a certain node is detached from active pgpool and then standby pgpool starts up, the standby pgpool can't recognized that the node is detached. Standby pgpool should get information about node information from other pgpool.<br />
<br />
=== Avoid multiple pgpools from executing failover.sh simultaneously. ===<br />
: In master-slave mode with watchdog, when a backend DB is down, all pgpools execute failover.sh. It might cause something wrong.<br />
<br />
=== Add new parameter for searching primary node timeout ===<br />
: pgpool-II uses "recovery_timeout" for searching the primary node timeout after failover. Since this is an abuse of the parameter, we should add new parameter for searching the primary node.<br />
<br />
=== Allow to load balance even in an explicit transaction in replication mode ===<br />
: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.<br />
<br />
=== Add testing framework ===<br />
: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.<br />
<br />
=== Add switch to control select(2) time out in connecting to PostgreSQL ===<br />
: In connect_inet_domain_socket_by_port(), select(2) is issued to watch events on the fd created by non blocking connect(2). The time out parameter of select(2) is fixed to 1 second, which is not long enough in flakey network environment like AWS (http://www.pgpool.net/pipermail/pgpool-general/2014-May/002880.html).<br />
: To solve the problem, new switch to control the time out is desired (done for pgpool-II 3.4.0).<br />
<br />
=== Allow to specify which node is dead when starting up ===<br />
: If we set longer health check timeout and/or many health check retries, starting up pgpool-II will take long time if some of DB nodes have been down because of health checking and retries in creating connection to backend.<br />
: pgpool_status should help here but for the very first starting up, we cannot use it.<br />
: It would be nice if we could tell pgpool-II about down node info (pgpool-II 3.4.0 chages the pgpool_status format to ASCII. Thus users can edit the file if needed).<br />
<br />
=== Remove parallel query ===<br />
: Parallel query has severe restrictions such as certain queries cannot be used, nor in extended protocol (i.e. JDBC).<br />
: Also it is pain to upgrade to newer version of PostgreSQL's SQL parser (yes, pgpool-II uses PostgreSQL's parser code). In short, parallel query gives us small gain comparing with the work needed to maintain/enhance. So I would like to obsolete parallel query in the future pgpool-II release. (related parameters have been removed from pgpool.conf in 3.4.0. pgpool-II 3.5.0 will remove actual code).<br />
<br />
=== Enhance pcp commands ===<br />
: There are number of drawbacks in pcp commands including 1)the timeout parameter is not used any more and should be removed 2)error codes returned from the commands are completely useless 3)multiple commands can not be accepted simultaneously.<br />
: This has been already done in 3.5.</div>
Usama
https://pgpool.net/mediawiki/index.php?title=TODO&diff=1017
TODO
2015-06-15T19:20:16Z
<p>Usama: /* Allow to use schema qualifications in black_function_list and white_function_list */</p>
<hr />
<div>__FORCETOC__<br />
<br />
== Pgpool-II TODO list ==<br />
<br />
=== Enhance performance of extended protocol case ===<br />
: When extended protocl (i.e. JDBC etc.) used, pgpool-II's overhead is pretty large compared with simple query. Need to enhance it.<br />
<br />
=== Automatically reattach a node in streaming master/slave configuration ===<br />
:In streaming master/slave configuration there could be an option to automatically reattach a node if it's up-to-date with the master (0 bytes behind). It often happens that due to minor network outage a slave node is dropped off from pgpool and stays down even if the the node has resumed replication with master and is up-to-date.pgpool already knows how much slave is behind master so i guess this wouldn't be too difficult to implement? (from bugtrack #17)<br />
<br />
=== Allow to use client encoding ===<br />
:It would be nice if pgpool client could use encoding which different from PostgreSQL server encoding.<br />
: To implement this, the parser should be able to handle "unsafe" encodings such as Shift_JIS. psql replaces second byte of each multibyte character to fool the parser. We could hire similar strategy.<br />
<br />
=== Send read query only to standbys even after fail over ===<br />
: We can configure pgpool-II to not send read queries to the primary. However after a fail over, the role of the node could be changed.<br />
: To solve the problem, we need new flag to specify that read queries always are sent to standbys regardless the fail over ([pgpool-general: 1621] backend weight after failover).<br />
<br />
=== Recognize multi statemnet queries ===<br />
: As stated in the document, pgpool-II does not recognize multi statement queries correctly (BEGIN;SELECT 1;END). Pgpool-II only parses the first element of the query ("BEGIN" in this case) and decides how to behave.<br />
: Of course this will bring various problems. It would be nice if pgpool-II could understand the each part of the multi statement queries.<br />
: Problem is, how PostgreSQL backend handles the multi statement queries. For example, when client sends BEGIN;SELECT 1;END, backend returns "Command Complete" respectively and "Ready for query" is returned only once. Thus, trying to split multi statement queries to non multi statement queries like what psql is doing will not work.<br />
<br />
=== Cursor statements are not load balanced, sent to all DB nodes in replication mode ===<br />
: DECLARE..FETCH are sent to all DB nodes in replication mode. This is because the SELECT might come with FOR UPDATE/FOR SHARE.<br />
: It would be nice if pgpool-II checks if the SELECT uses FOR UPDATE/FOR SHARE and if not, enable load balance (or only sends to the master node if load balance is disabled).<br />
: Note that some applications including psql could use CURSOR for SELECT. For example, from PostgreSQL 8.2, if "\set FETCH_COUNT n" is executed, psql unconditionaly uses a curor named "_psql_cursor".<br />
<br />
=== Support IPv6 network ===<br />
: As of 3.4, it is allowed to use IPv6 address for PostgreSQL backend server and bind address of pgpool-II itself.<br />
: However, PCP process still only binds to IPv4 and UNIX domain socket.<br />
<br />
=== Handle abnormal down of virtual IP interface when watchdog enabled ===<br />
: When virtual IP interface is dropped abnormally by manual ifconfig etc., there are no one holding VIP, and clients aren't able to connect pgpool-II. Watchdog of active pgpool should monitor the interface or VIP, and handle its down.<br />
<br />
=== Do not invalidate query cache created in a transaction in some cases ===<br />
: Currently new query cache for table t1 created in a transaction is removed at commit if there's DMLs which touch t1 in the same transaction. Apparently this is overkill for same cases:<br />
BEGIN;<br />
INSERT INTO t1 VALUES(1);<br />
SELECT * FROM t1;<br />
COMMIT;<br />
: To enhance this, we need to teach pgpool-II about "order of SELECTs and DMLs.".<br />
<br />
=== Fix memory leak in pool_config.c ===<br />
: The module in charge of parsing pgpool.conf has memory leak problem. Usually pgpool reads pgpool.conf just once at the start up time, it is not a big problem. However reloading pgpool.conf will leak memory and definitely a problem. Also using memory leak check tools like valgrind emit lots of error messages and very annoying. So it would be nice to fix the problem in the future.<br />
<br />
=== Add SET commnad ===<br />
: Pgpool specific SET command would be usefull. For example, using "SET debug = 1" could produce debug info on the fly for particular session.<br />
<br />
=== Put together a definition of error codes into a single header file ===<br />
: Currently most error codes used by pool_send_{error,fatal}_message() etc (e.g. "XX000", "XX001", "57000") are hard-coded in different sources. They should be defined as constants in a single header together.<br />
<br />
=== Create separate process for health checking ===<br />
: To make main process more stable, it would be better to make separate process which is responsible for health checking.<br />
<br />
=== Import PostgreSQL's latch module ===<br />
: Pgpool already has similar module but PostgreSQL's one seems more sophiscated and reliable.<br />
<br />
=== Import PostgreSQL 9.5's parser ===<br />
: No need to say for this.<br />
<br />
=== Allow to use schema qualifications in black_function_list and white_function_list ===<br />
: Currently schema qualifications are silently ignored in these parameter.<br />
<br />
=== Watchdog feature enhancement ===<br />
Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture.<br />
See the design proposal for watchdog enhancement [[http://pgpool.net/mediawiki/index.php/watchdog_feature_enhancement]]<br />
<br />
== TODOs already done ==<br />
<br />
=== Allow to specify which node is dead when starting up ===<br />
: If we set longer health check timeout and/or many health check retries, starting up pgpool-II will take long time if some of DB nodes have been down because of health checking and retries in creating connection to backend.<br />
: pgpool_status should help here but for the very first starting up, we cannot use it.<br />
: It would be nice if we could tell pgpool-II about down node info.<br />
: As of 3.4, pgpool_status file is changed to a plain ASCII file and users could specify down node by using ordinary text editors.<br />
<br />
=== Ability to load balance based on Client IP, database, table etc. ===<br />
: From bugid 26: I have recently moved a database from Mysql to postgresql 9.1.5 which is behind a pgpool-II-3.1.4 . Everything went fine until i observed that some "tickets" are not created correctly by the application (OTRS) that populate the database.<br />
: After some debugging i found/guess that the problem is the following:<br />
: when a cron job wants to create a ticket he has to insert info in abut 10 tables, and i guess that the 2-nd, 3-rd ... inserts depends on the first. The problem was that this operation is not performed transactionally so after the first insert, when the app tries to perform the other inserts, first tries to select "the first insert", but this first insert is still not propagated to all nodes, and the error occurs.<br />
: I`m aware of the fact that if this entire operation would be performed transactionally (only on master) the issue is solved, but unfortunately i cannot modify the app.<br />
: So i want to know if there is any way that i can tell to pgpool something like :<br />
: any request from this ip do not load balance.<br />
<br />
: PS. temporary i have set the weight factor to 0 to the 2-nd and 3-rd postgresql slaves and it behaves ok, because reads and writes only from master.<br />
<br />
: P.P.S. there's also different request regarding load balance.<br />
: http://www.pgpool.net/pipermail/pgpool-general/2014-June/003032.html<br />
<br />
: This item has been implemented in 3.4 as "database_redirect_preference_list" and "app_name_redirect_preference_list".<br />
<br />
=== Import PostgreSQL's execption handling ===<br />
: PostgreSQL's exception handling (elog family) is pretty good tool to make codes to be simple and robust. It would be nice if pgpool could use this. This has been already done in 3.4.=== Allow to print user name in the logging ===<br />
: This will be useful for audit purpose. (done and will appear in pgpool-II-3.4.0).<br />
<br />
=== Remove on disk query cache ===<br />
: Old on disk query cache has almost 0 user and has sevior limitation, including no automatic cache invalidation. This has been already obsoleted since on memory query cache implemented. We should remove this (this has been already in git master and will appear in 3.4.0).<br />
<br />
=== Restart watchdog process when it abnormaly exits ===<br />
: It would be nice for pgpool main to restart watchdog process when it dies abormaly.<br />
<br />
=== Synchronize backend nodes information with watchdog when standby pgpool starts up ===<br />
: For example, when a certain node is detached from active pgpool and then standby pgpool starts up, the standby pgpool can't recognized that the node is detached. Standby pgpool should get information about node information from other pgpool.<br />
<br />
=== Avoid multiple pgpools from executing failover.sh simultaneously. ===<br />
: In master-slave mode with watchdog, when a backend DB is down, all pgpools execute failover.sh. It might cause something wrong.<br />
<br />
=== Add new parameter for searching primary node timeout ===<br />
: pgpool-II uses "recovery_timeout" for searching the primary node timeout after failover. Since this is an abuse of the parameter, we should add new parameter for searching the primary node.<br />
<br />
=== Allow to load balance even in an explicit transaction in replication mode ===<br />
: Currently load balance in an explicit transaction is only allowed in master-slave mode. It should be allowed in the replication mode as well.<br />
<br />
=== Add testing framework ===<br />
: PostgreSQL has nice regression test suite. It would be nice if pgpool-II has similar test suite. Problem is, such a suite could be very complex system because it should include not only pgpool-II itself, but also multiple PostgreSQL instances. Also don't forget about "watchdog". Even such a test suite should be able to manage multiple pgpool-II instances.<br />
<br />
=== Add switch to control select(2) time out in connecting to PostgreSQL ===<br />
: In connect_inet_domain_socket_by_port(), select(2) is issued to watch events on the fd created by non blocking connect(2). The time out parameter of select(2) is fixed to 1 second, which is not long enough in flakey network environment like AWS (http://www.pgpool.net/pipermail/pgpool-general/2014-May/002880.html).<br />
: To solve the problem, new switch to control the time out is desired (done for pgpool-II 3.4.0).<br />
<br />
=== Allow to specify which node is dead when starting up ===<br />
: If we set longer health check timeout and/or many health check retries, starting up pgpool-II will take long time if some of DB nodes have been down because of health checking and retries in creating connection to backend.<br />
: pgpool_status should help here but for the very first starting up, we cannot use it.<br />
: It would be nice if we could tell pgpool-II about down node info (pgpool-II 3.4.0 chages the pgpool_status format to ASCII. Thus users can edit the file if needed).<br />
<br />
=== Remove parallel query ===<br />
: Parallel query has severe restrictions such as certain queries cannot be used, nor in extended protocol (i.e. JDBC).<br />
: Also it is pain to upgrade to newer version of PostgreSQL's SQL parser (yes, pgpool-II uses PostgreSQL's parser code). In short, parallel query gives us small gain comparing with the work needed to maintain/enhance. So I would like to obsolete parallel query in the future pgpool-II release. (related parameters have been removed from pgpool.conf in 3.4.0. pgpool-II 3.5.0 will remove actual code).<br />
<br />
=== Enhance pcp commands ===<br />
: There are number of drawbacks in pcp commands including 1)the timeout parameter is not used any more and should be removed 2)error codes returned from the commands are completely useless 3)multiple commands can not be accepted simultaneously.<br />
: This has been already done in 3.5.</div>
Usama
https://pgpool.net/mediawiki/index.php?title=watchdog_feature_enhancement&diff=1016
watchdog feature enhancement
2015-06-15T19:16:17Z
<p>Usama: /* What is required by the watchdog? */</p>
<hr />
<div>==== What's driving this enhancement ====<br />
:Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture. So this enhancement of watchdog is aimed at providing the stability and robustness to the existing pgpool-II watchdog with some new cool features.<br />
<br />
== Some pgpool-II general mailing list threads related to watchdog ==<br />
<br />
* [pgpool-general: 3724] delegate ip lost<br />
* [pgpool-II 0000135]: Delegate IP does not get up on Standby upon Active gets disconnected (same in ppgool-general: 3736)<br />
* Split-brain scenario due to network partitioning <br />
* [ppgool-general: 3595] Watchdog issue.<br />
* [pgpool-general: 3443] watchdog on cloud<br />
* [pgpool-general: 3126] watchdog voting<br />
* [pgpool-general: 2985] Re: Connections stuck in CLOSE_WAIT, again<br />
* [pgpool-general: 2949] Re: pgpool 3.3.3 watchdog problem<br />
* [pgpool-general: 2797] pcp_watchdog_info parameters<br />
* [pgpool-general: 2768] timeout Watchdog<br />
* [pgpool-general: 2427] watchdog quorum<br />
* [pgpool-general: 2418] Re: watchdog: different statuses on different pgpool nodes.<br />
* [pgpool-general: 3772] Race condition for VIP assignment<br />
* Lots of question on suid or root privileges are required ([pgpool-general: 3323] Re: Watchdog - ifconfig up failed)<br />
* User wants ACTIVE-ACTIVE pgpool-II configuration and miscellaneous comments on the difficulty in configuration of watchdog<br />
<br />
'''Summary''' <br />
Analyzing above pgpool-II community threads related to watchdog, It comes down to four main areas where current pgpool-II watchdog requires some enhancements.<br />
*1-- Related to Virtual IP assignments and handling the case of lost of VIP<br />
*2-- Split-brain scenario, recovery from it and watchdog quorum<br />
*3-- Users run into misconfigured watchdog situations very often.<br />
*4-- Wants watchdog on cloud and active-active watchdog configurations<br />
<br />
'''Still open Issues'''<br />
* [pgpool-general: 3724] delegate ip lost<br />
* [pgpool-general: 3772] Race condition for VIP assignment<br />
* [pgpool-general: 3228] Split brain or using 3 nodes ?<br />
* [pgpool-general: 3728] Re: pgpool-general Digest, Vol 43, Issue 17<br />
<br />
==== '''Design proposal for enhanced watchdog''' ====<br />
==== Terminologies used below ====<br />
'''Cluster''': Cluster is the logical entity which contains all the pgpool-II server nodes connected by pgpool-II watchdog.<br />
<br />
====What is required by the watchdog?====<br />
<br />
To provide the HA watchdog is required to ensure following.<br />
<br />
* Ensure only healthy nodes are part of the cluster<br />
* Ensure only authorized nodes can become the member of the cluster<br />
* Ensure only one pgpool-II node is a designated master node at any time<br />
* Provide the automatic recovery mechanism when possible when some problem occurs<br />
<br />
==== Watchdog need to provide a guard against following types of failures ====<br />
<br />
* pgpool-II service failure<br />
* complete or partial network failures.<br />
<br />
==== High level responsibilities of the watchdog ====<br />
<br />
* Health checking of all participating pgpool-II nodes in the cluster including the health checking of local pgpool-II server.<br />
* Ensure the availability of delegate-ip always on a single node at all the time.<br />
* Mechanism to add and remove pgpool-II nodes from the cluster.<br />
* Perform the leader election to select the master node when the cluster is initialized or in case of master node failure.<br />
* Performs an automatic recovery if the due to some issue the cluster state is broken or split-brain scenario happens<br />
* Generate alarms for failures where administrator intervention is required to rectify the problem.<br />
* Manage the pgpool-II configurations to make sure all the nodes in the cluster have similar configurations.<br />
* Provide the effective way of health checking of other nodes (heartbeat) and messaging between participating nodes.<br />
* Ensure security so that only intended nodes can become the cluster members.<br />
* Provide the mechanism so that administrator can check the status of the cluster and alarms generated by cluster.<br />
* Able to remove the node membership from the cluster(node fencing) if a problematic node is detected or requested by administrator command.<br />
<br />
==== Watchdog on Amazon Cloud and other cloud flavours ====<br />
<br />
This is the much asked for feature that pgpool-II watchdog should work seamlessly on AWS. So the enhanced watchdog will work on amazon cloud where a simple virtual IP can not be used by pgpool-II watchdog. For this the enhanced watchdog will implement two new features.<br />
<br />
*Active-Active watchdog configuration: This will be a big improvement to the pgpool-II watchdog and this would effectually mean that multiple pgpool-II servers can be installed and external load-balancer and HA system can be used with the pgpool-II<br />
*New watchdog will be flexible enough to allow utilities other than ifconfig (e.g ec2-assign-private-ip-addresses for AWS virtual IP) can be used to bring up virtual-IP<br />
<br />
==== Logical Components of watchdog ====<br />
<br />
The pgpool-II watchdog system will consists of following discrete logical components<br />
<br />
* Heartbeat to monitor health and availability of cluster member nodes.<br />
* Messaging system, to share status and configurations between cluster member nodes.<br />
** All the messaging will be in xml or text based extensible protocol to ensure easy debugging and future extensions<br />
** Will provide a communication mechanism for unicast as well as broadcast messaging<br />
* Local resource manager, which will have a responsibility to monitor the health of local resources. It will consist of two sub components<br />
** delegate-IP monitoring and control<br />
** Local pgpool-II server monitoring<br />
* Information database, That will store and manage all the cluster wide runtime information and pgpool-II configurations<br />
* IPC listener to enable administrator control by PCP commands.<br />
<br />
==== Working overview of watchdog system ====<br />
<br />
The new watchdog system will be a finite state machine which will transit between different states. Some prominent systems states will be<br />
<br />
*IDLE -- nothing is happening<br />
*STARTING -- starting up<br />
*STOPING -- stoping<br />
*ELECTION -- Take part in the election<br />
*JOINING CLUSTER -- we are initialised and joining the cluster<br />
*ELECTED MASTER -- If the node has been just elected as the master node<br />
*NORMAL NODE -- If we are not master and have joined the cluster as a slave node<br />
*RECOVERY -- some event occurred and we are recovering from it<br />
<br />
==The basic working of the watchdog will be as follows ==<br />
<br />
* At startup do basic sanity checks and go into the normal member node state, wait for the instructions from the master node or start the election algorithm.<br />
* If the election algorithm is started, Participate in the elections and become either master node or normal node, depending on election results.<br />
* Once the election is complete, if we are the master node, move to the master waiting state and construct the complete view of member nodes and cluster state<br />
* Construct the information database and propagate it to all member nodes.<br />
* Start the health-checking of local resources and remote nodes and stay in this state until some failure occur. Depending upon type of failure or event takes appropriate actions. ''The action could be one of the following''<br />
** Kill itself.<br />
** Start leader election<br />
** Restart a local resource (pgpool-II server or delegate-IP)<br />
** Inform about some event or failure to master node (if it is not master node)<br />
** Replicate the configuration or information to the member nodes (master node only)<br />
** Perform fencing of member node (master node only)<br />
<br />
==== Responsibilities of master watchdog node ====<br />
* Maintaining the up to date configurations of pgpool-II and replicating it to all participating nodes in the cluster<br />
* Health checking of backend pgpool-II nodes, And if the configuration is in such a way that all members are required to do backend health checking, or if the backend error is detected by any other member of cluster, then ensure that failover of the backend node is executed only by a single node.<br />
* Managing the fencing, joining and leaving of members from the cluster<br />
* Keeping hold of delegate-IP and making sure that it is recovered back if for some reason it is dropped.<br />
* Handing over the responsibility to some other cluster member if for some issue, it is not able to continue as master node or instruct by administrator command.<br />
<br />
==== Leader election algorithm ====<br />
Selecting the best algorithm for selecting the master pgpool-II node in case of master node failure or at start-up is still a TODO, and one of the suggestion is to use Leader Election in Asynchronous Distributed Systems http://www.cs.indiana.edu/pub/techreports/TR521.pdf algorithm (Also used by pacemaker). <br />
:Other leader selection algorithm suggestions are most welcome</div>
Usama
https://pgpool.net/mediawiki/index.php?title=watchdog_feature_enhancement&diff=1015
watchdog feature enhancement
2015-06-15T19:10:40Z
<p>Usama: /* Some pgpool-II general mailing list threads related to watchdog */</p>
<hr />
<div>==== What's driving this enhancement ====<br />
:Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture. So this enhancement of watchdog is aimed at providing the stability and robustness to the existing pgpool-II watchdog with some new cool features.<br />
<br />
== Some pgpool-II general mailing list threads related to watchdog ==<br />
<br />
* [pgpool-general: 3724] delegate ip lost<br />
* [pgpool-II 0000135]: Delegate IP does not get up on Standby upon Active gets disconnected (same in ppgool-general: 3736)<br />
* Split-brain scenario due to network partitioning <br />
* [ppgool-general: 3595] Watchdog issue.<br />
* [pgpool-general: 3443] watchdog on cloud<br />
* [pgpool-general: 3126] watchdog voting<br />
* [pgpool-general: 2985] Re: Connections stuck in CLOSE_WAIT, again<br />
* [pgpool-general: 2949] Re: pgpool 3.3.3 watchdog problem<br />
* [pgpool-general: 2797] pcp_watchdog_info parameters<br />
* [pgpool-general: 2768] timeout Watchdog<br />
* [pgpool-general: 2427] watchdog quorum<br />
* [pgpool-general: 2418] Re: watchdog: different statuses on different pgpool nodes.<br />
* [pgpool-general: 3772] Race condition for VIP assignment<br />
* Lots of question on suid or root privileges are required ([pgpool-general: 3323] Re: Watchdog - ifconfig up failed)<br />
* User wants ACTIVE-ACTIVE pgpool-II configuration and miscellaneous comments on the difficulty in configuration of watchdog<br />
<br />
'''Summary''' <br />
Analyzing above pgpool-II community threads related to watchdog, It comes down to four main areas where current pgpool-II watchdog requires some enhancements.<br />
*1-- Related to Virtual IP assignments and handling the case of lost of VIP<br />
*2-- Split-brain scenario, recovery from it and watchdog quorum<br />
*3-- Users run into misconfigured watchdog situations very often.<br />
*4-- Wants watchdog on cloud and active-active watchdog configurations<br />
<br />
'''Still open Issues'''<br />
* [pgpool-general: 3724] delegate ip lost<br />
* [pgpool-general: 3772] Race condition for VIP assignment<br />
* [pgpool-general: 3228] Split brain or using 3 nodes ?<br />
* [pgpool-general: 3728] Re: pgpool-general Digest, Vol 43, Issue 17<br />
<br />
====What is required by the watchdog?====<br />
<br />
To provide the HA watchdog is required to ensure following.<br />
<br />
* Ensure only healthy nodes are part of the cluster<br />
* Ensure only authorized nodes can become the member of the cluster<br />
* Ensure only one pgpool-II node is a designated master node at any time<br />
* Provide the automatic recovery mechanism when possible when some problem occurs<br />
<br />
==== Watchdog need to provide a guard against following types of failures ====<br />
<br />
* pgpool-II service failure<br />
* complete or partial network failures.<br />
<br />
==== High level responsibilities of the watchdog ====<br />
<br />
* Health checking of all participating pgpool-II nodes in the cluster including the health checking of local pgpool-II server.<br />
* Ensure the availability of delegate-ip always on a single node at all the time.<br />
* Mechanism to add and remove pgpool-II nodes from the cluster.<br />
* Perform the leader election to select the master node when the cluster is initialized or in case of master node failure.<br />
* Performs an automatic recovery if the due to some issue the cluster state is broken or split-brain scenario happens<br />
* Generate alarms for failures where administrator intervention is required to rectify the problem.<br />
* Manage the pgpool-II configurations to make sure all the nodes in the cluster have similar configurations.<br />
* Provide the effective way of health checking of other nodes (heartbeat) and messaging between participating nodes.<br />
* Ensure security so that only intended nodes can become the cluster members.<br />
* Provide the mechanism so that administrator can check the status of the cluster and alarms generated by cluster.<br />
* Able to remove the node membership from the cluster(node fencing) if a problematic node is detected or requested by administrator command.<br />
<br />
==== Watchdog on Amazon Cloud and other cloud flavours ====<br />
<br />
This is the much asked for feature that pgpool-II watchdog should work seamlessly on AWS. So the enhanced watchdog will work on amazon cloud where a simple virtual IP can not be used by pgpool-II watchdog. For this the enhanced watchdog will implement two new features.<br />
<br />
*Active-Active watchdog configuration: This will be a big improvement to the pgpool-II watchdog and this would effectually mean that multiple pgpool-II servers can be installed and external load-balancer and HA system can be used with the pgpool-II<br />
*New watchdog will be flexible enough to allow utilities other than ifconfig (e.g ec2-assign-private-ip-addresses for AWS virtual IP) can be used to bring up virtual-IP<br />
<br />
==== Logical Components of watchdog ====<br />
<br />
The pgpool-II watchdog system will consists of following discrete logical components<br />
<br />
* Heartbeat to monitor health and availability of cluster member nodes.<br />
* Messaging system, to share status and configurations between cluster member nodes.<br />
** All the messaging will be in xml or text based extensible protocol to ensure easy debugging and future extensions<br />
** Will provide a communication mechanism for unicast as well as broadcast messaging<br />
* Local resource manager, which will have a responsibility to monitor the health of local resources. It will consist of two sub components<br />
** delegate-IP monitoring and control<br />
** Local pgpool-II server monitoring<br />
* Information database, That will store and manage all the cluster wide runtime information and pgpool-II configurations<br />
* IPC listener to enable administrator control by PCP commands.<br />
<br />
==== Working overview of watchdog system ====<br />
<br />
The new watchdog system will be a finite state machine which will transit between different states. Some prominent systems states will be<br />
<br />
*IDLE -- nothing is happening<br />
*STARTING -- starting up<br />
*STOPING -- stoping<br />
*ELECTION -- Take part in the election<br />
*JOINING CLUSTER -- we are initialised and joining the cluster<br />
*ELECTED MASTER -- If the node has been just elected as the master node<br />
*NORMAL NODE -- If we are not master and have joined the cluster as a slave node<br />
*RECOVERY -- some event occurred and we are recovering from it<br />
<br />
==The basic working of the watchdog will be as follows ==<br />
<br />
* At startup do basic sanity checks and go into the normal member node state, wait for the instructions from the master node or start the election algorithm.<br />
* If the election algorithm is started, Participate in the elections and become either master node or normal node, depending on election results.<br />
* Once the election is complete, if we are the master node, move to the master waiting state and construct the complete view of member nodes and cluster state<br />
* Construct the information database and propagate it to all member nodes.<br />
* Start the health-checking of local resources and remote nodes and stay in this state until some failure occur. Depending upon type of failure or event takes appropriate actions. ''The action could be one of the following''<br />
** Kill itself.<br />
** Start leader election<br />
** Restart a local resource (pgpool-II server or delegate-IP)<br />
** Inform about some event or failure to master node (if it is not master node)<br />
** Replicate the configuration or information to the member nodes (master node only)<br />
** Perform fencing of member node (master node only)<br />
<br />
==== Responsibilities of master watchdog node ====<br />
* Maintaining the up to date configurations of pgpool-II and replicating it to all participating nodes in the cluster<br />
* Health checking of backend pgpool-II nodes, And if the configuration is in such a way that all members are required to do backend health checking, or if the backend error is detected by any other member of cluster, then ensure that failover of the backend node is executed only by a single node.<br />
* Managing the fencing, joining and leaving of members from the cluster<br />
* Keeping hold of delegate-IP and making sure that it is recovered back if for some reason it is dropped.<br />
* Handing over the responsibility to some other cluster member if for some issue, it is not able to continue as master node or instruct by administrator command.<br />
<br />
==== Leader election algorithm ====<br />
Selecting the best algorithm for selecting the master pgpool-II node in case of master node failure or at start-up is still a TODO, and one of the suggestion is to use Leader Election in Asynchronous Distributed Systems http://www.cs.indiana.edu/pub/techreports/TR521.pdf algorithm (Also used by pacemaker). <br />
:Other leader selection algorithm suggestions are most welcome</div>
Usama
https://pgpool.net/mediawiki/index.php?title=watchdog_feature_enhancement&diff=1014
watchdog feature enhancement
2015-06-15T15:30:34Z
<p>Usama: /* Some pgpool-II general mailing list threads related to watchdog */</p>
<hr />
<div>==== What's driving this enhancement ====<br />
:Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture. So this enhancement of watchdog is aimed at providing the stability and robustness to the existing pgpool-II watchdog with some new cool features.<br />
<br />
== Some pgpool-II general mailing list threads related to watchdog ==<br />
<br />
: -- [pgpool-general: 3724] delegate ip lost<br />
: -- [pgpool-II 0000135]: Delegate IP does not get up on Standby upon Active gets disconnected (same in ppgool-general: 3736)<br />
: -- Split-brain scenario due to network partitioning <br />
: -- [ppgool-general: 3595] Watchdog issue.<br />
: -- [pgpool-general: 3443] watchdog on cloud<br />
: -- [pgpool-general: 3126] watchdog voting<br />
: -- [pgpool-general: 2985] Re: Connections stuck in CLOSE_WAIT, again<br />
: -- [pgpool-general: 2949] Re: pgpool 3.3.3 watchdog problem<br />
: -- [pgpool-general: 2797] pcp_watchdog_info parameters<br />
: -- [pgpool-general: 2768] timeout Watchdog<br />
: -- [pgpool-general: 2427] watchdog quorum<br />
: -- [pgpool-general: 2418] Re: watchdog: different statuses on different pgpool nodes.<br />
: -- [pgpool-general: 3772] Race condition for VIP assignment<br />
: -- Lots of question on suid or root privileges are required ([pgpool-general: 3323] Re: Watchdog - ifconfig up failed)<br />
: -- User wants ACTIVE-ACTIVE pgpool-II configuration and miscellaneous comments on the difficulty in configuration of watchdog<br />
<br />
:'''Summary''' <br />
<br />
:Analyzing above pgpool-II community threads related to watchdog, It comes down to four main areas where current pgpool-II watchdog requires some enhancements.<br />
: 1-- Related to Virtual IP assignments and handling the case of lost of VIP<br />
: 2-- Split-brain scenario, recovery from it and watchdog quorum<br />
: 3-- Users run into misconfigured watchdog situations very often.<br />
: 4-- Wants watchdog on cloud and active-active watchdog configurations<br />
<br />
:'''Still open Issues'''<br />
<br />
: -- [pgpool-general: 3724] delegate ip lost<br />
: -- [pgpool-general: 3772] Race condition for VIP assignment<br />
: -- [pgpool-general: 3228] Split brain or using 3 nodes ?<br />
: -- [pgpool-general: 3728] Re: pgpool-general Digest, Vol 43, Issue 17<br />
<br />
What is required by the watchdog?<br />
---------------------------------------------------<br />
The main purpose of the watchdog in pgpool-II is to provide high availability, For this purpose the watchdog is required to ensure following.<br />
<br />
-- Ensure only healthy nodes are part of the cluster<br />
-- Ensure only authorized nodes can become the member of the cluster<br />
-- Ensure only one pgpool-II node is a designated master node at any time<br />
-- Provide the automatic recovery mechanism when possible when some problem occurs</div>
Usama
https://pgpool.net/mediawiki/index.php?title=watchdog_feature_enhancement&diff=1013
watchdog feature enhancement
2015-06-15T15:26:23Z
<p>Usama: Created page with "==== What's driving this enhancement ==== :Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are ..."</p>
<hr />
<div>==== What's driving this enhancement ====<br />
:Watchdog is a very important feature of pgpool-II as it is used to eliminate the single point of failure and provide HA. But there are few feature requests and bugs in the existing watchdog that require little more than a simple code fix, and requires the complete revisit of its core architecture. So this enhancement of watchdog is aimed at providing the stability and robustness to the existing pgpool-II watchdog with some new cool features.<br />
<br />
== Some pgpool-II general mailing list threads related to watchdog ==<br />
<br />
: -- [pgpool-general: 3724] delegate ip lost<br />
: -- [pgpool-II 0000135]: Delegate IP does not get up on Standby upon Active gets disconnected (same in ppgool-general: 3736)<br />
: -- Split-brain scenario due to network partitioning <br />
: -- [ppgool-general: 3595] Watchdog issue.<br />
: -- [pgpool-general: 3443] watchdog on cloud<br />
: -- [pgpool-general: 3126] watchdog voting<br />
: -- [pgpool-general: 2985] Re: Connections stuck in CLOSE_WAIT, again<br />
: -- [pgpool-general: 2949] Re: pgpool 3.3.3 watchdog problem<br />
: -- [pgpool-general: 2797] pcp_watchdog_info parameters<br />
: -- [pgpool-general: 2768] timeout Watchdog<br />
: -- [pgpool-general: 2427] watchdog quorum<br />
: -- [pgpool-general: 2418] Re: watchdog: different statuses on different pgpool nodes.<br />
: -- [pgpool-general: 3772] Race condition for VIP assignment<br />
: -- Lots of question on suid or root privileges are required ([pgpool-general: 3323] Re: Watchdog - ifconfig up failed)<br />
: -- User wants ACTIVE-ACTIVE pgpool-II configuration and miscellaneous comments on the difficulty in configuration of watchdog<br />
<br />
:'''Summary''' <br />
<br />
:Analyzing above pgpool-II community threads related to watchdog, It comes down to four main areas where current pgpool-II watchdog requires some enhancements.<br />
: 1-- Related to Virtual IP assignments and handling the case of lost of VIP<br />
: 2-- Split-brain scenario, recovery from it and watchdog quorum<br />
: 3-- Users run into misconfigured watchdog situations very often.<br />
: 4-- Wants watchdog on cloud and active-active watchdog configurations<br />
<br />
''':Still open Issues'''<br />
<br />
: -- [pgpool-general: 3724] delegate ip lost<br />
: -- [pgpool-general: 3772] Race condition for VIP assignment<br />
: -- [pgpool-general: 3228] Split brain or using 3 nodes ?<br />
: -- [pgpool-general: 3728] Re: pgpool-general Digest, Vol 43, Issue 17</div>
Usama
https://pgpool.net/mediawiki/index.php?title=User_talk:Usama&diff=1012
User talk:Usama
2015-06-15T14:31:56Z
<p>Usama: /* watchdog feature enhancement */</p>
<hr />
<div></div>
Usama
https://pgpool.net/mediawiki/index.php?title=User_talk:Usama&diff=1011
User talk:Usama
2015-06-15T14:26:01Z
<p>Usama: Created page with "==== watchdog feature enhancement===="</p>
<hr />
<div>==== [[watchdog feature enhancement]]====</div>
Usama