| | | | 0000001 | 1 | 2 |
| 微調整 | 新規 | 2012-02-20 | Make pid_file optional |
| | | | 0000002 | 2 | |
| メジャー | | 2012-02-14 | Client connection hangs in daemon mode |
| | | | 0000003 | 3 | |
| マイナー | 完了 | 2012-03-29 | health checks to new master disconnect abnormally after master failover |
| | | | 0000004 | 3 | |
| メジャー | | 2012-02-22 | pgpool doesn't exit on term signal even if all connections are idle |
| | | | 0000005 | 9 | 3 |
| マイナー | 完了 | 2012-03-29 | occasional pgpool child segmentation faults |
| | | | 0000006 | 1 | |
| メジャー | 解決済 (kitagawa) | 2012-02-23 | Selects is not balanced among a session |
| | | | 0000007 | 1 | |
| メジャー | 解決済 (kitagawa) | 2012-12-10 | Occasionally get error: prepared statement "S_133" does not exist. |
| | | | 0000008 | 2 | 3 |
| マイナー | | 2012-12-18 | update pgpool.spec |
| | | | 0000009 | 1 | |
| システム停止 | | 2012-11-26 | dont call syslog(3) family in signal handler. |
| | | | 0000010 | 1 | |
| マイナー | | 2012-08-29 | SQL log doesnt work with JDBC |
| | | | 0000011 | 4 | 1 |
| マイナー | 完了 | 2012-06-26 | pgpool-)II 3.1.2 does not see my pool_hba.conf file |
| | | | 0000012 | | |
| マイナー | 新規 | 2012-05-10 | Backend nodes can be considered failed during startup |
| | | | 0000013 | 1 | 1 |
| 要望 | | 2012-05-23 | ERROR: portal "" does not exist {prepstmnt 1698892272 |
| | | | 0000014 | 17 | |
| メジャー | | 2012-10-05 | pgpool beeaks unnamed prepared statements used by the application |
| | | | 0000015 | 15 | 1 |
| メジャー | | 2013-09-12 | pgpool-II 3.1.3 on FreeBSD regex patterns for blacklist/whitelist report errors |
| | | | 0000016 | 2 | |
| メジャー | | 2012-08-24 | pgpool unable to reuse cached connections for non-default databases, and special treatment of default databases |
| | | | 0000017 | 1 | |
| 要望 | | 2012-11-26 | Automatically reattach a node in streaming master/slave configuration |
| | | | 0000018 | 1 | |
| メジャー | | 2012-12-18 | pgpool-II deadlock on extended queries |
| | | | 0000019 | 2 | |
| メジャー | | 2012-11-21 | with latest pgpool-II3.2RC1 faced portal "" does not exist |
| | | | 0000020 | 1 | 1 |
| メジャー | | 2012-11-26 | pgpool does not accept connections after postgres hits the max_connections limit |
| | | | 0000021 | 9 | 3 |
| メジャー | | 2012-10-02 | pgpool-II 3.2.0 cannot execute sql through jdbc |
| | | | 0000022 | 1 | 1 |
| クラッシュ | | 2012-11-15 | *** glibc detected *** pgpool: ... idle in transaction: double free or corruption |
| | | | 0000023 | 15 | |
| クラッシュ | | 2012-12-18 | Segfault with pg-pool-II version 3.2 |
| | | | 0000024 | 18 | 11 |
| メジャー | | 2012-10-05 | Severe memory leak in an OLTP environment |
| | | | 0000025 | 6 | |
| マイナー | | 2012-09-10 | s_do_auth doesn't handle NoticeResponse (N) message |
| | | | 0000026 | 1 | |
| 要望 | | 2012-09-04 | ability to load balance query based on host ip |
| | | | 0000027 | 2 | |
| マイナー | | 2012-11-14 | Pgpool 3.2 memory cache logs |
| | | | 0000028 | 19 | 6 |
| マイナー | | 2013-02-01 | general protection & Segfault |
| | | | 0000029 | 6 | |
| メジャー | | 2012-12-05 | pgpool 3.2.1 cannot connect to db hosts |
| | | | 0000030 | 3 | 1 |
| マイナー | | 2012-10-26 | pgpool 3.2.1 - views in schema other than public are caching |
| | | | 0000031 | 12 | 3 |
| クラッシュ | | 2013-02-09 | pgpool V3_2_STABLE - segfault in pool_memqcache.c:2529 |
| | | | 0000032 | 2 | 3 |
| クラッシュ | | 2012-11-15 | PGPool hangs on pcp_attach/detach |
| | | | 0000034 | 1 | |
| 表示 | | 2012-11-18 | pg_md5 has a -f option, but it doesn't show up in the help text |
| | | | 0000035 | 10 | 3 |
| マイナー | | 2013-04-04 | Authentication is timeout |
| | | | 0000036 | 2 | |
| マイナー | | 2012-12-18 | pcp_node_count o/p is hanging after pcp_detach_node |
| | | | 0000037 | 1 | |
| マイナー | | 2012-11-21 | pgpool2-{3.0.4,3.2.1} doesn't compile without pam (./configure --without-pam) |
| | | | 0000038 | 7 | 3 |
| メジャー | | 2012-11-23 | pgpool causes erroneous commit when DROP FUNCTION is sent |
| | | | 0000039 | | |
| マイナー | | 2012-12-18 | wd_lifecheck is wrong after failover |
| | | | 0000040 | | |
| マイナー | | 2012-12-18 | typo of ./configure |
| | | | 0000041 | | |
| マイナー | | 2012-12-18 | pg_md5 behavior |
| | | | 0000042 | | |
| マイナー | | 2013-02-01 | watchdog's split brain |
| | | | 0000043 | | |
| マイナー | | 2012-12-06 | /etc/alternatives/pgpool-pcp_systemdb_info link incorrect |
| | | | 0000044 | 9 | |
| クラッシュ | | 2014-11-14 | pgpool went haywire after slave shutdown triggering master failover |
| | | | 0000045 | 10 | 2 |
| メジャー | | 2013-01-16 | LISTEN/NOTIFY doesn' t work if cluster contains more then 1 node in streaming replication mode |
| | | | 0000046 | 7 | 1 |
| メジャー | | 2013-01-23 | Watchdog failing to connect sometimes |
| | | | 0000047 | 1 | 1 |
| システム停止 | | 2012-12-21 | spelling error in pgpoolAdmin-3.2.1 source file - common.php |
| | | | 0000048 | 4 | 3 |
| クラッシュ | | 2013-02-01 | watchdog crash |
| | | | 0000049 | 1 | 1 |
| 要望 | | 2015-01-08 | "ifconfig" is obsolete; replace with "ip" |
| | | | 0000050 | 12 | 3 |
| メジャー | | 2013-04-04 | pgpool connectivity issue when health check enabled |
| | | | 0000051 | 8 | 7 |
| クラッシュ | | 2013-03-15 | pgpool crashes on DDL statements |
| | | | 0000052 | 2 | 2 |
| クラッシュ | | 2013-03-15 | Out of memory issue ,,, |
| | | | 0000053 | 9 | |
| システム停止 | | 2013-05-14 | pgpool_regclass hangs all connections |
| | | | 0000054 | 4 | 3 |
| メジャー | | 2013-06-26 | pgpool-II semaphore lock problem |
| | | | 0000055 | 6 | 1 |
| メジャー | | 2015-09-17 | Child process ##### was terminated by segmentation fault |
| | | | 0000056 | 3 | 1 |
| マイナー | | 2013-04-19 | UPDATE with alias does not discard cache |
| | | | 0000057 | 1 | 1 |
| システム停止 | | 2013-04-29 | "cannot get parse message" error when using py-postgresql |
| | | | 0000058 | 9 | 2 |
| メジャー | | 2013-06-12 | query cache invalidation does not fire for multiple DML in transaction |
| | | | 0000060 | 3 | 2 |
| メジャー | | 2013-07-02 | Exceptions on COMMIT cause abnormal pgpool process termination and disconnects |
| | | | 0000061 | 2 | 1 |
| メジャー | | 2013-07-02 | Child process xxxx was terminated by segmentation fault |
| | | | 0000062 | 4 | 2 |
| メジャー | | 2013-07-24 | Slave network outage causes a segmentation fault on main process |
| | | | 0000063 | 3 | 1 |
| クラッシュ | | 2013-06-30 | Child process was terminated by segmentation fault with memcached |
| | | | 0000064 | 5 | |
| メジャー | | 2013-07-19 | Using |
| | | | 0000065 | | |
| メジャー | | 2013-08-02 | [pgpool-general: 1948] tight lockup of main pgpool process |
| | | | 0000066 | 1 | |
| マイナー | | 2015-01-08 | [pgpool-general: 1978] pgpool 3.3.0 RC1 master/master - reset when on db is down |
| | | | 0000067 | 1 | |
| マイナー | | 2015-01-08 | [pgpool-general: 1961] pgpool-II 3.3.0 and parallel mode |
| | | | 0000068 | 1 | 1 |
| メジャー | | 2013-08-05 | child process termination with sigabort when memory_cache_enabled = on |
| | | | 0000069 | 4 | |
| メジャー | | 2015-01-08 | Portal "X_#####" does not exist |
| | | | 0000070 | 2 | 1 |
| メジャー | | 2013-10-19 | on memory caching can fill up, expired items not purged. |
| | | | 0000071 | 3 | 1 |
| メジャー | | 2013-11-03 | Sometime healcheck failed and backend |
| | | | 0000072 | 6 | 1 |
| システム停止 | | 2013-09-19 | query cache invalidation fails on fq table name |
| | | | 0000073 | 1 | |
| メジャー | | 2013-09-09 | external cache invalidation mechanism |
| | | | 0000074 | 1 | |
| マイナー | | 2013-09-25 | pgpool 3.2.6 - segfault in pool_worker_child.c |
| | | | 0000075 | 3 | |
| マイナー | | 2013-10-07 | Do not find master_node if not needed |
| | | | 0000076 | 4 | 3 |
| メジャー | | 2013-10-19 | pgpool 3.3.1 has segfault under load of UPDATEs to psql 9.2 database. |
| | | | 0000077 | 6 | 1 |
| クラッシュ | | 2015-09-17 | Hibernate lost connection with pgpool without persistence |
| | | | 0000078 | 1 | |
| マイナー | | 2013-10-22 | script install |
| | | | 0000079 | 5 | |
| マイナー | | 2015-09-17 | Pgpool 3.2 memory cache log: pool_delete_item_shmem_cache |
| | | | 0000080 | 7 | |
| メジャー | | 2013-11-09 | memqcache_auto_cache_invalidation is unsettable |
| | | | 0000081 | 8 | 1 |
| メジャー | | 2013-11-11 | Random failure on first INSERT after a BEGIN TRANSACTION |
| | | | 0000082 | | |
| マイナー | 新規 | 2013-11-11 | segfault in pool_auth.c if master is down |
| | | | 0000083 | 1 | |
| マイナー | 新規 | 2013-11-11 | Set KeepAlive for backend (postgresql) |
| | | | 0000084 | 8 | 1 |
| メジャー | | 2013-12-04 | Watchdog race condition - other members never leave 'not started' state |
| | | | 0000085 | 1 | 1 |
| 要望 | | 2014-04-02 | Integrate |
| | | | 0000086 | 1 | 1 |
| 要望 | | 2014-04-02 | Monitor |
| | | | 0000087 | 7 | 1 |
| メジャー | | 2014-01-23 | "unnamed prepared statement does not exist" |
| | | | 0000088 | 1 | 1 |
| 要望 | | 2014-04-02 | Monitor |
| | | | 0000089 | 1 | 1 |
| 要望 | | 2014-04-02 | Monitor |
| | | | 0000090 | 1 | |
| クラッシュ | | 2014-05-20 | pool_extract_error_message: not enough buffer space |
| | | | 0000091 | 3 | |
| メジャー | 完了 | 2014-01-28 | Can't use pgpool-ha with CentoOS 6.5 ccs/pacemaker (Error: Unable to parse xml for: pgpool) |
| | | | 0000092 | 1 | |
| メジャー | | 2014-05-07 | enbugs pgpool-II 3.3.2 at JDBC by statement.executeUpdate(simple_dml) |
| | | | 0000093 | 1 | |
| メジャー | | 2014-02-26 | Prepared statements don't respect partitioning rules |
| | | | 0000094 | 4 | 1 |
| クラッシュ | | 2015-01-08 | Segfaults when using ORDER in parallel mode |
| | | | 0000095 | 5 | 1 |
| メジャー | | 2015-09-17 | Query Cache does not recognize when a Materialized view has been refreshed. |
| | | | 0000096 | 1 | 1 |
| 要望 | | 2014-04-02 | Monitor |
| | | | 0000097 | 1 | |
| システム停止 | | 2014-10-07 | node.js: error: unnamed prepared statement does not exist |
| | | | 0000098 | 3 | |
| メジャー | | 2014-04-25 | memqcache_auto_cache_invalidation doesn't work properly |
| | | | 0000099 | 3 | |
| メジャー | | 2016-05-06 | PGPool HA v2.2 unable to parse xml output |
| | | | 0000100 | 1 | |
| 些細 | | 2014-05-12 | is_superuser not available in nodeStatus.php |
| | | | 0000101 | 10 | |
| メジャー | | 2014-05-18 | random kind mismatch among backends. Possible last query was: "SET default_transaction_isolation TO DEFAULT" |
| | | | 0000102 | 6 | 1 |
| メジャー | | 2014-06-11 | pgpool-II(3.3.3) failover does not work properly many times. |
| | | | 0000103 | 3 | |
| メジャー | | 2015-09-17 | Pgpool 3.1.6 - connect_inet_domain_socket: connect() failed: Invalid argument |
| | | | 0000104 | 1 | 1 |
| 些細 | | 2014-06-14 | Missing include in 3.3.3 sources |
| | | | 0000105 | 6 | 3 |
| システム停止 | | 2015-01-08 | Failover dead lock |
| | | | 0000106 | 12 | 1 |
| メジャー | | 2015-08-04 | pgpool - v 3.3.3 hangs and does not allow more connection |
| | | | 0000107 | 11 | 3 |
| メジャー | | 2020-10-15 | Stuck connections |
| | | | 0000108 | 3 | |
| クラッシュ | | 2015-07-15 | PGPool crashes on pcp_attach_node after all backends have been detached |
| | | | 0000109 | 6 | |
| マイナー | | 2014-08-24 | Query prefixed with any comment (/* ... */) triggers NO LOAD BALANCE mode |
| | | | 0000110 | 1 | 1 |
| マイナー | | 2014-08-12 | Postgres unwanted query execute |
| | | | 0000111 | 1 | |
| マイナー | | 2015-06-29 | Significant increase of load average after upgrade to PSQL 9.3 and Pgpool 3.3.3 |
| | | | 0000112 | 4 | |
| メジャー | | 2014-08-22 | Pgpool reports wrong primary node |
| | | | 0000113 | 2 | 1 |
| マイナー | | 2014-09-15 | Split rpm packages also to "pgpool-II-${pg_version}-extensions" |
| | | | 0000114 | 2 | 1 |
| マイナー | | 2014-10-22 | Can't disable debug logging after enabling it with a config reload |
| | | | 0000115 | 1 | |
| 微調整 | 解決済 | 2014-10-07 | RPM spec file has extra flags for SSL |
| | | | 0000116 | 1 | |
| メジャー | | 2015-04-28 | LISTEN Notifications Not Reliably Delivered Using JDBC4 Demonstrator |
| | | | 0000117 | 2 | |
| マイナー | | 2014-11-28 | Can't build pgpool-II 3.3.4 with new libmemcached |
| | | | 0000118 | 13 | 2 |
| システム停止 | | 2015-02-26 | Pgpool does not connect with Tableau client with postgress driver. |
| | | | 0000119 | 6 | 1 |
| マイナー | | 2014-11-28 | Signal might be sent to pid=1 (init process) in send_failback_request() |
| | | | 0000120 | | |
| メジャー | | 2014-11-06 | Standby pgpool fail to start after failover |
| | | | 0000121 | 2 | |
| メジャー | | 2014-12-02 | Failback process igonre node status and lag limit |
| | | | 0000122 | 1 | |
| マイナー | | 2015-04-28 | pgpool-II 3.4.0 - if_up_cmd and if_down_cmd $_IP_$ substitution is too optimistic |
| | | | 0000123 | 4 | 1 |
| メジャー | | 2018-07-06 | MD5 authentication is not requiring password. |
| | | | 0000124 | 5 | 1 |
| メジャー | | 2015-08-21 | Stuck connections - Same as issue 0000107 but with pgPool 3.4.0 |
| | | | 0000125 | 1 | 1 |
| メジャー | | 2015-01-08 | stand for master problem |
| | | | 0000126 | 5 | 2 |
| クラッシュ | | 2023-09-25 | pgpool get stuck after failover |
| | | | 0000127 | 1 | 1 |
| 微調整 | | 2015-01-05 | pgpool-II fail in regression '004.watchdog'. |
| | | | 0000128 | 1 | |
| マイナー | | 2015-04-22 | Error during online recovery |
| | | | 0000129 | 9 | 4 |
| クラッシュ | | 2016-01-29 | pgpool child out of memory |
| | | | 0000130 | | |
| マイナー | | 2015-04-18 | failover command triggered, when pg backend reaches max_connections |
| | | | 0000131 | 1 | |
| マイナー | | 2015-04-27 | Issue doing a PITR online recovery - xlog function cannot be found |
| | | | 0000132 | 4 | |
| システム停止 | | 2015-04-17 | Cannot connect using -h localhost with pgpool 3.4.2 |
| | | | 0000133 | 4 | 2 |
| マイナー | | 2016-03-25 | Get empty parameters for failover.sh: Master and slave can not define a new primary node |
| | | | 0000134 | 3 | |
| マイナー | | 2015-06-11 | down pgpool wd node failback failed |
| | | | 0000135 | 7 | 1 |
| メジャー | | 2015-12-16 | Delegate IP does not get up on Standby upon Active gets disconnected |
| | | | 0000136 | 1 | 1 |
| メジャー | | 2015-06-20 | pgpool's use of to_regclass ignores double quotes |
| | | | 0000137 | 4 | |
| クラッシュ | | 2015-06-29 | Too much memory consumption by PgPool process |
| | | | 0000138 | 2 | |
| 表示 | | 2015-10-15 | Address already in use |
| | | | 0000139 | 1 | |
| マイナー | | 2015-11-18 | broken arping_cmd doesn't get reported in pgpool 3.3.6 |
| | | | 0000140 | | 1 |
| メジャー | | 2015-08-04 | Child process memory grows without bound in v3.3.4 |
| | | | 0000141 | | |
| メジャー | | 2015-08-04 | Passive pgpool node execute failover on DB nodes |
| | | | 0000142 | 7 | |
| メジャー | | 2015-08-21 | rpm's require libmemcache 2 |
| | | | 0000143 | 3 | 1 |
| マイナー | | 2015-08-20 | pgpool2 3.3.7 test/timestamp fails to compile |
| | | | 0000144 | 1 | |
| メジャー | | 2015-09-17 | Bug with inserting via PQexecParams |
| | | | 0000145 | 6 | 1 |
| メジャー | | 2015-10-16 | Didn't sent reset_query to Standby node. |
| | | | 0000146 | 4 | |
| メジャー | | 2016-01-18 | Don't work parameterized query in transaction |
| | | | 0000147 | 11 | 5 |
| メジャー | | 2016-01-25 | pgpool connection pool exhausted when connections should have been dropped |
| | | | 0000148 | 1 | |
| マイナー | | 2015-10-14 | Documentation bug in pcp_node_info |
| | | | 0000149 | 1 | |
| マイナー | | 2015-10-14 | Incorrect error for "Watchdog" command failures |
| | | | 0000150 | 5 | |
| マイナー | | 2015-10-14 | yum install incorrectly links pcp_watchdog_info binary |
| | | | 0000151 | 2 | 1 |
| 表示 | | 2015-11-25 | Error message has typo - "md5 authentication failed" |
| | | | 0000152 | 15 | 3 |
| メジャー | | 2016-12-16 | Error with JDBC memory_cache_enabled = on |
| | | | 0000153 | 3 | 1 |
| マイナー | | 2015-10-14 | pgpool doesn't replicate data-modifying CTEs |
| | | | 0000154 | 3 | |
| マイナー | | 2016-02-17 | pgpool fails to parse query used by recent versions of DBD::Pg to ping DB |
| | | | 0000155 | 1 | 1 |
| システム停止 | 新規 | 2022-01-21 | failover: set new primary node: -1 |
| | | | 0000156 | 10 | 1 |
| マイナー | | 2016-01-17 | Pgpool reload during high load causes the fatal error |
| | | | 0000157 | 14 | |
| マイナー | | 2016-05-13 | pgpool routes queries with "SET TRANSACTION READ ONLY" to master |
| | | | 0000158 | 1 | |
| マイナー | | 2016-05-06 | pgpool web console gets pgpool.conf parameters incorrectly |
| | | | 0000159 | 4 | |
| マイナー | | 2016-01-17 | message ' getsockopt() detected error "Operation now in progress" ' |
| | | | 0000161 | 2 | |
| メジャー | | 2016-05-11 | Always PostgreSQL1 node is down frequently from PGpool console |
| | | | 0000162 | 5 | 1 |
| マイナー | | 2016-01-04 | To start watchdog pgpool nodes simultaneously is not safe |
| | | | 0000163 | 2 | |
| システム停止 | | 2016-05-11 | Connections not released if client exit ungracefully. |
| | | | 0000164 | 1 | 1 |
| マイナー | | 2016-02-01 | watchdog authentication failed |
| | | | 0000165 | 1 | 1 |
| メジャー | | 2016-01-29 | Performance degradation(x250) while using ipv6 |
| | | | 0000166 | 1 | |
| 微調整 | | 2016-02-03 | V3_5_0 doesn't compile under freebsd |
| | | | 0000167 | 47 | 6 |
| メジャー | | 2016-03-30 | PgPool does not return during Hibernate initialisation, stuck on "Parsing" |
| | | | 0000168 | 5 | 1 |
| メジャー | | 2016-03-03 | 3.5.0 issues with php-pdo |
| | | | 0000169 | 3 | |
| メジャー | | 2016-03-07 | 3.5.0 issues with php-pdo/2 - constraint violation version |
| | | | 0000170 | 3 | |
| マイナー | | 2019-06-17 | md5 authentication without using pool_passwd |
| | | | 0000171 | 1 | 1 |
| メジャー | | 2016-03-07 | Start/Stop/Restart PgSQL from PGAdmin not working |
| | | | 0000172 | 2 | |
| マイナー | | 2016-03-18 | failback_command finishes,pgpool-II DONNOT restart all child processes. |
| | | | 0000174 | 2 | |
| システム停止 | | 2016-03-18 | pgpool child processes exit unexpectedly and don't restart after online recovery of a standby node |
| | | | 0000175 | 5 | 1 |
| クラッシュ | | 2016-04-02 | Hibernate + Pgpool-II Connection Failure |
| | | | 0000176 | 2 | |
| マイナー | | 2016-05-06 | What is the execution order of ‘follow_master_command' and 'failover_command'? |
| | | | 0000177 | 6 | |
| メジャー | | 2019-02-15 | Pgpool stops accepting connections when Postgresql slave goes down |
| | | | 0000178 | 2 | 1 |
| マイナー | | 2016-06-09 | Enironment Variable PG_CONFIG Ignored |
| | | | 0000179 | 3 | |
| マイナー | | 2016-03-28 | Run Continuously attaching two degenerate backend，the second backend WILLNOT SUCCESS。 |
| | | | 0000181 | | |
| マイナー | 新規 | 2016-03-24 | failover_command and follow_master_command are RARELY executed at the pgpool standby |
| | | | 0000182 | 5 | 2 |
| マイナー | | 2016-03-29 | Pgpool child hangs with full cpu load after permission error message from backend |
| | | | 0000183 | 8 | 1 |
| システム停止 | | 2016-06-21 | Pgppol not sending query error back to client |
| | | | 0000184 | 3 | |
| マイナー | 完了 | 2017-10-18 | when failover happened, the trigger will disappear |
| | | | 0000185 | 2 | |
| メジャー | | 2016-05-06 | plugs out the network cable，the pgpool will not work。 |
| | | | 0000186 | | |
| マイナー | 新規 | 2016-03-29 | when failover done，online recovery will log error “BackendError the NO. is 12” |
| | | | 0000187 | 9 | |
| メジャー | | 2016-12-27 | pcp_* functions call interface changed in pgpool 3.5 but pgpooladmin use old call mechanism |
| | | | 0000188 | 4 | 1 |
| メジャー | | 2016-04-20 | pcp_proc_count truncates PIDs over 5 characters long |
| | | | 0000189 | 3 | 1 |
| マイナー | | 2016-04-15 | kind mismatch error on master_slave_mode=on / load_lalance_mode=off |
| | | | 0000190 | 9 | 3 |
| メジャー | | 2016-04-21 | PgPool hangs in load balance mode, when using JDBC driver and sending empty query. |
| | | | 0000191 | | |
| マイナー | | 2016-04-14 | pgpool-II shouldn't forward set default_transaction_isolation to 'serializable' to Hot Standby slaves |
| | | | 0000192 | 6 | 3 |
| 些細 | | 2016-07-28 | Human readable option for pcp_node_info [Patch included] |
| | | | 0000193 | 1 | |
| メジャー | 完了 | 2016-05-21 | pgpool trigger failover after killing user session in the master postgres server |
| | | | 0000194 | 21 | 4 |
| メジャー | | 2016-06-05 | "statement timeout" causes kind mismatch errors |
| | | | 0000195 | 5 | |
| マイナー | | 2016-06-10 | pgpool routes queries with "SET TRANSACTION READ ONLY" to master |
| | | | 0000196 | 8 | |
| メジャー | | 2016-07-12 | md5 authentication is broken |
| | | | 0000197 | 1 | 1 |
| メジャー | | 2016-06-16 | pgpool hangs connections to database when interface of standby/second backend |
| | | | 0000198 | | |
| メジャー | 新規 | 2016-05-16 | connect_inet_domain_socket_by_port: health check timer expired |
| | | | 0000199 | 1 | |
| メジャー | 完了 | 2016-05-21 | Best Pgpool-II version for our Environment & Performance issue |
| | | | 0000201 | 1 | |
| システム停止 | | 2016-05-25 | 'Recover' button greyed out always in gui 'Node status' |
| | | | 0000202 | 7 | 2 |
| メジャー | | 2017-08-29 | failed to create INET domain socket |
| | | | 0000203 | 4 | |
| メジャー | | 2017-08-29 | Connections stuck - Recv-Q fills up |
| | | | 0000204 | 2 | |
| マイナー | | 2016-06-08 | healthcheck get stuck |
| | | | 0000205 | 2 | |
| クラッシュ | | 2016-08-05 | Cannot accept() new connection. all backends are down restart |
| | | | 0000206 | 2 | |
| クラッシュ | | 2016-08-05 | write on frontend failed with error :"Broken pipe" |
| | | | 0000207 | 5 | |
| システム停止 | | 2016-06-20 | pgpool tries to bind twice to the listening socket on debian |
| | | | 0000208 | 1 | |
| マイナー | | 2016-07-01 | What is the Enhancements / Changes in 3.5.3 w.r.t 3.5.2 of PGPool II |
| | | | 0000209 | 6 | 2 |
| メジャー | | 2016-12-20 | Query cache invalidation performed too late |
| | | | 0000211 | 9 | 3 |
| メジャー | | 2016-09-28 | YCSB can't connect to PGPool-II in master-slave mode. |
| | | | 0000212 | 2 | 3 |
| クラッシュ | | 2016-09-28 | pgpool runs out of memory |
| | | | 0000213 | 6 | 1 |
| システム停止 | | 2017-03-26 | ERROR: node recovery failed, waiting connection closed in the other pgpools timeout |
| | | | 0000214 | 2 | |
| メジャー | | 2016-09-28 | plugs out the network cable, pgpool not change backend status and blocking connections |
| | | | 0000215 | 4 | 3 |
| メジャー | | 2016-08-01 | pgpool doesnt escalate ip in case of another node inavailability |
| | | | 0000216 | | |
| マイナー | | 2016-07-15 | this is test |
| | | | 0000217 | | |
| マイナー | | 2016-07-15 | test2 |
| | | | 0000218 | 8 | 1 |
| メジャー | | 2016-08-02 | Inconsistent status of Postgresql nodes in pgPool instances after restart. Watchdog not syncing status. |
| | | | 0000219 | 1 | |
| メジャー | 完了 | 2016-07-26 | Inconsistent status of Postgresql nodes in pgPool instances after restart. Watchdog not syncing status. |
| | | | 0000220 | 4 | |
| マイナー | | 2017-08-15 | socket read failed with an error "No error: 0" (pgpool 3.5 stable) |
| | | | 0000221 | 8 | |
| クラッシュ | | 2016-08-11 | kind mismatch among backends. Possible last query was: "COMMIT" kind details are: 0[C] 1[N: ] |
| | | | 0000222 | 4 | 1 |
| メジャー | | 2016-08-12 | Sometimes Failover command isn't executed. |
| | | | 0000223 | 11 | |
| メジャー | | 2016-12-20 | PgPool performs load balancing even when it's disabled |
| | | | 0000224 | 1 | |
| マイナー | 完了 | 2016-07-27 | pgpool segfault |
| | | | 0000225 | 5 | 2 |
| マイナー | | 2016-09-09 | pgpool segfault |
| | | | 0000226 | 2 | |
| メジャー | | 2016-09-06 | pgpool doesn't support jdbc well trigger jdbc 'exception' |
| | | | 0000227 | 41 | 10 |
| メジャー | | 2017-08-29 | failover not performed by stanby node |
| | | | 0000228 | 3 | 1 |
| メジャー | | 2016-08-04 | pgpool doesnt de-escalate IP in case netowkr restored |
| | | | 0000229 | 2 | 1 |
| クラッシュ | | 2016-09-21 | Buffer Overflow on backend_hostname greater than 64 characters |
| | | | 0000230 | 4 | 2 |
| メジャー | | 2016-08-09 | pgpool does not return result set if the statement fetchSize is smaller than the result row count. |
| | | | 0000231 | 47 | 9 |
| メジャー | | 2016-12-20 | packet kind of backend 1 ['3'] does not match with master/majority nodes packet kind ['2'] |
| | | | 0000232 | 2 | |
| マイナー | | 2016-08-15 | pcp_stop_pgpool emit an error message: ERROR: unable to read data from socket. |
| | | | 0000233 | 18 | 1 |
| メジャー | | 2016-08-16 | an error message: ERROR: unable to read data from frontend DETAIL: EOF encountered with frontend. |
| | | | 0000234 | 2 | 3 |
| システム停止 | | 2017-08-29 | pgpool fails to run failover script if the sever running primary pgpool node and postgresql server dies |
| | | | 0000235 | 4 | 1 |
| マイナー | 完了 | 2016-08-29 | Forking new child process every 60 seconds |
| | | | 0000236 | 1 | |
| メジャー | | 2016-08-29 | pg_md5 - out of memeory |
| | | | 0000237 | 1 | |
| マイナー | | 2016-08-30 | Pgpool-II fails to start if listen_addresses is empty string |
| | | | 0000238 | 10 | 4 |
| 要望 | | 2016-09-06 | Performance of selects queries |
| | | | 0000239 | 12 | |
| メジャー | | 2021-04-08 | invalid pcp socket directory |
| | | | 0000240 | 7 | 1 |
| メジャー | | 2017-08-29 | Connections remains open when backend dettach during a transaction |
| | | | 0000241 | 2 | |
| マイナー | | 2016-09-27 | The repository package not works correctly |
| | | | 0000242 | 3 | |
| マイナー | | 2016-09-06 | show pool_nodes tells both nodes are standby |
| | | | 0000243 | 7 | |
| メジャー | | 2016-09-09 | pgpool ignores backend weight in balancing |
| | | | 0000244 | 17 | 8 |
| メジャー | | 2017-03-30 | Load balancing error |
| | | | 0000245 | 1 | |
| マイナー | 完了 | 2016-12-20 | 3.5.4 not in pgdg repo yet |
| | | | 0000246 | 8 | 1 |
| メジャー | | 2016-12-20 | PGPool "idle in transaction" |
| | | | 0000247 | 2 | 1 |
| マイナー | 完了 | 2016-09-21 | Automatic recovery of the failed node without any manual intervention. |
| | | | 0000248 | 3 | 1 |
| メジャー | | 2016-09-28 | pgpool doesnt restores backend connections |
| | | | 0000249 | 31 | 6 |
| メジャー | | 2017-02-24 | watchdog sometimes fails de-escalation. |
| | | | 0000250 | 1 | 3 |
| メジャー | | 2017-08-29 | Not proper behaviour of Pgpool when one node of cluster goes disconnect by down interface |
| | | | 0000251 | 8 | 3 |
| メジャー | | 2017-08-29 | failover_command not executed |
| | | | 0000252 | 1 | |
| マイナー | | 2016-10-18 | authentication failed error when PCP command is cancelled by other pgpool |
| | | | 0000253 | 1 | |
| マイナー | 完了 | 2016-12-20 | SSL for watchdog lifechecks |
| | | | 0000254 | 11 | |
| マイナー | | 2018-02-16 | Same as http://www.pgpool.net/mantisbt/view.php?id=53 |
| | | | 0000255 | 8 | |
| マイナー | 完了 | 2016-12-05 | Understanding of max_pool |
| | | | 0000256 | 1 | |
| メジャー | 完了 | 2016-10-20 | Load Balancing option with master slave doesn't work for Functions that write. |
| | | | 0000257 | 3 | |
| メジャー | | 2016-10-26 | Notify not received |
| | | | 0000258 | 2 | |
| マイナー | | 2017-04-07 | While attaching nodes in replication mode "show pool_nodes" is showing different values on each node |
| | | | 0000259 | 4 | 1 |
| メジャー | | 2016-11-10 | status of nodes in load balancing mode |
| | | | 0000260 | 4 | 1 |
| マイナー | | 2017-08-15 | Issue 0000248 reproduced in "pgpool-II version 3.6beta2 (subaruboshi)" |
| | | | 0000261 | 7 | 1 |
| システム停止 | | 2017-02-23 | Random break of connections with error "kind mismatch among backends" |
| | | | 0000262 | 7 | |
| メジャー | | 2016-12-06 | md5 authentification is broken REOPEN of 0000196 |
| | | | 0000263 | 7 | 5 |
| クラッシュ | | 2016-12-20 | Segfault when query cache enabled |
| | | | 0000264 | 2 | |
| マイナー | | 2016-11-24 | FATAL: -1 is outside the valid range for parameter "client_idle_limit_in_recovery" (0 .. 2147483647) occurs in 3.6.0 |
| | | | 0000265 | 3 | 1 |
| マイナー | | 2017-01-12 | pgpool-II sometimes hangs on restart |
| | | | 0000266 | 1 | 1 |
| マイナー | | 2017-02-15 | Standby server Pgpool shutdown when master server postgresql down due to ipc key conflict |
| | | | 0000267 | | |
| マイナー | | 2017-08-29 | log_destination is set to syslog but pgpool does not use /dev/log |
| | | | 0000268 | | |
| メジャー | | 2020-12-10 | pgpool block on issue_command_to_watchdog() for ever when the primary's network is cut off |
| | | | 0000269 | | 1 |
| マイナー | | 2017-05-18 | authentication timeout with connection_life_time |
| | | | 0000270 | 8 | |
| システム停止 | | 2017-05-01 | pgpool system hung cause parallel many query |
| | | | 0000271 | 38 | 4 |
| メジャー | | 2017-03-31 | balanced requests after started transaction |
| | | | 0000272 | 3 | 1 |
| メジャー | | 2017-02-23 | pgpool not releasing shared memory segments |
| | | | 0000273 | 3 | 2 |
| メジャー | | 2017-08-29 | ERROR: unable to read data from frontend |
| | | | 0000274 | 9 | 1 |
| メジャー | | 2021-10-08 | PgPool showing all the nodes as standby even though pg_is_in_recovery() shows correctly as master/standby? |
| | | | 0000275 | 2 | |
| メジャー | 完了 | 2017-01-06 | PgPool not starting and showing failed to bind a socket: "/var/run/pgpool/.s.PGSQL.5433" |
| | | | 0000276 | 3 | 2 |
| マイナー | | 2017-08-29 | superuser: unknown (Connection error) in pgpoolAdmin |
| | | | 0000277 | 2 | |
| マイナー | | 2017-02-28 | pgpoolAdmin is missing in yum repository pgpool36 |
| | | | 0000278 | 2 | |
| マイナー | 完了 | 2017-01-06 | ifconfig_path is ignored after upgrade |
| | | | 0000279 | 3 | |
| 要望 | | 2017-02-08 | Opionally dismiss 57P01 as a clean disconnection when failover_on_backend_error is off and health checks are enabled |
| | | | 0000280 | 7 | 1 |
| システム停止 | | 2017-01-27 | stack smashing detected |
| | | | 0000281 | 3 | 1 |
| マイナー | | 2017-08-29 | "segmentation fault" when execute pcp_attach_node |
| | | | 0000282 | 11 | 4 |
| メジャー | | 2017-03-26 | Pgpool hangs on query and doesn't send it to backend |
| | | | 0000283 | 1 | 2 |
| メジャー | | 2017-08-29 | PGPool hangs in Master/Slave mode with Slony submodule |
| | | | 0000284 | 4 | 5 |
| メジャー | | 2017-03-15 | pgpool-II native replication loses sync every 1-2 days |
| | | | 0000285 | 1 | |
| マイナー | 完了 | 2017-02-08 | after failover standby not become primary |
| | | | 0000286 | 10 | 2 |
| メジャー | | 2017-05-01 | pgpool hangs with hibernate and spring |
| | | | 0000287 | 2 | |
| メジャー | | 2017-03-26 | Syntax Error in Query Using CURRENT_TIMESTAMP |
| | | | 0000288 | 7 | |
| メジャー | | 2017-04-07 | FATAL: failed to read kind from backend |
| | | | 0000289 | 2 | 6 |
| メジャー | | 2017-04-13 | Inconsistent backend state |
| | | | 0000290 | | |
| メジャー | | 2017-03-23 | [safety violation] master without quorum execute failover procedure |
| | | | 0000291 | 3 | 1 |
| システム停止 | | 2017-05-01 | ERROR: portal "pgpool_error_portal" does not exist |
| | | | 0000292 | 2 | 1 |
| マイナー | | 2017-03-13 | pcp_promote_node fails when trying promoting node 0 |
| | | | 0000293 | 4 | 2 |
| マイナー | | 2017-08-29 | PgpoolAdmin shows Port instead Status (MASTER/SLAVE) of Pgpool Servers in Watchdog |
| | | | 0000294 | | |
| メジャー | | 2017-03-23 | Pgpool service fails to start on the load of OS |
| | | | 0000295 | 3 | 1 |
| メジャー | | 2017-03-23 | Watchdog service fails to start |
| | | | 0000296 | 11 | 2 |
| マイナー | | 2017-08-29 | PGPool v3.6.2 terminated by systemd because the service Type has been set to 'forking' |
| | | | 0000297 | 9 | 1 |
| マイナー | | 2017-08-29 | Notice: Undefined variable: msgPcpPassFile in $PATH/checkParameter.php on line 427 |
| | | | 0000298 | 3 | |
| マイナー | | 2017-08-29 | pcp_watchdog_info command error occurred. Notice: Undefined offset: 2 in $PATH/command.php on line 156 |
| | | | 0000299 | 7 | 1 |
| マイナー | | 2017-08-29 | Errors on the reloading of configuration |
| | | | 0000300 | 4 | |
| メジャー | | 2017-05-16 | pgpool-II doesn't handle lost socket file |
| | | | 0000301 | 5 | 1 |
| クラッシュ | | 2017-08-15 | Segfault when memcached is enabled in 3.6.2-1.pgdg14.04+1 |
| | | | 0000302 | 1 | |
| メジャー | | 2017-07-03 | failover with watchdog causes inconsistent backend status |
| | | | 0000303 | 9 | 1 |
| マイナー | | 2017-08-03 | db_node_is is not properly initialized |
| | | | 0000304 | 15 | 5 |
| マイナー | | 2017-08-04 | Hibernate is hanging in connect PGPOOL-II |
| | | | 0000305 | 18 | 6 |
| システム停止 | | 2018-03-21 | inconsistent node status with watchdog configuration |
| | | | 0000306 | 39 | 12 |
| メジャー | | 2017-08-29 | Pgpool steals back MASTER status |
| | | | 0000307 | 6 | 1 |
| クラッシュ | | 2017-06-26 | pgpool failed after pool_check_fd call failed with an error "Interrupted system call" |
| | | | 0000308 | 4 | 2 |
| システム停止 | | 2017-05-17 | pgpool-II not started |
| | | | 0000309 | 1 | |
| メジャー | | 2017-08-29 | bind socket failed with error: "Address already in use" |
| | | | 0000310 | 3 | |
| システム停止 | | 2017-07-19 | INSERT ... ON CONFLICT ... DO UPDATE queries hang |
| | | | 0000311 | 1 | |
| メジャー | 完了 | 2017-06-13 | Pgpool-II에서 Failover 기능 되지 않음. |
| | | | 0000312 | 3 | |
| システム停止 | | 2017-07-19 | Node stays at 0 on pgpool |
| | | | 0000313 | 2 | 1 |
| メジャー | | 2017-06-09 | hang with extended protocol |
| | | | 0000314 | 2 | 1 |
| メジャー | | 2017-06-07 | kind mismatch error with extended protocol when close for portal is issued |
| | | | 0000315 | 2 | |
| メジャー | | 2017-08-29 | High CPU usage when commiting large transactions and using in (shared) memory cache |
| | | | 0000316 | 10 | 2 |
| メジャー | | 2017-08-29 | One postgresql backend node is marked down often |
| | | | 0000317 | 11 | 9 |
| メジャー | | 2017-08-29 | pgpool sometimes fails to return a "Ready for query" causing client to hang. |
| | | | 0000318 | 15 | 4 |
| システム停止 | | 2017-08-29 | Exception in plpgsql function is not passed to application |
| | | | 0000319 | 5 | 1 |
| システム停止 | 完了 | 2017-07-19 | pgpool hangs in pool_check_fd() |
| | | | 0000320 | 9 | 1 |
| メジャー | | 2017-08-30 | Index Error Violations are never returned to the application |
| | | | 0000321 | 4 | 1 |
| システム停止 | | 2017-12-08 | If pgpool is running on another machine than the application some queries hand for good |
| | | | 0000322 | 9 | |
| メジャー | | 2018-06-22 | PGPool child processes go into <defunct> state when a backend node is unresponsive |
| | | | 0000323 | 1 | |
| メジャー | | 2017-08-29 | After error : the connection is marked as "idle in transaction (aborted)" |
| | | | 0000324 | 12 | 1 |
| メジャー | | 2017-08-04 | backend consumes large amount of RAM with long sessions |
| | | | 0000325 | 4 | |
| メジャー | | 2017-08-09 | pool_check_fd call failed with an error "Interrupted system call" |
| | | | 0000326 | 1 | 1 |
| クラッシュ | | 2018-05-01 | pcp_node_info command error occurred on pgpool admin |
| | | | 0000327 | 25 | 2 |
| メジャー | | 2017-10-03 | Cannot connect to PGPool when caching is enabled |
| | | | 0000328 | 3 | 1 |
| マイナー | | 2017-08-14 | Malformed packet in response to simple query containing only '-- comment' |
| | | | 0000329 | | 1 |
| メジャー | | 2017-08-15 | Newly elected(promoted) Pgpool does connect to any backend |
| | | | 0000330 | 17 | 2 |
| システム停止 | | 2017-08-24 | Unable to connect to pgpool-II using jdbc |
| | | | 0000331 | 1 | |
| 些細 | | 2017-08-23 | The socket location is not changing while running pcp commands |
| | | | 0000332 | 3 | |
| メジャー | | 2017-12-14 | Watch dog issue |
| | | | 0000333 | 2 | 2 |
| メジャー | | 2017-09-08 | watchdog fails to add node to master when wd_authkey is not an empty string; pgpool member shuts down |
| | | | 0000334 | 7 | |
| メジャー | | 2017-12-08 | after upgrate postgresql to 9.6 , pgpool detect "all backends are down " aftre run a few hour or one day |
| | | | 0000335 | 6 | |
| クラッシュ | | 2017-09-06 | PgPool II not connecting with the application! |
| | | | 0000336 | 12 | 1 |
| クラッシュ | | 2017-11-13 | During load the server in production would fail connectivity with a slave and itself, resulting in removing nodes |
| | | | 0000337 | | |
| メジャー | | 2019-01-30 | PgPool health check hangs at pool_check_fd() resulting in pgpool zombie child processes |
| | | | 0000338 | 4 | |
| マイナー | | 2018-12-04 | watchdog virtual IP |
| | | | 0000339 | 6 | 15 |
| システム停止 | | 2018-01-11 | Failover does not occurr if master Pgpool-II and primary PostgreSQL servers are stopped at the same time |
| | | | 0000340 | 1 | 1 |
| メジャー | 完了 | 2017-10-05 | pgpool failover scenario ERROR - pgpool 3.6.6 (postgres 9.3.5) |
| | | | 0000341 | 3 | |
| システム停止 | 完了 | 2017-09-23 | Incompatibility with ruby pg |
| | | | 0000342 | 2 | 1 |
| メジャー | | 2017-11-09 | On master fail slave not able to convert itself to master |
| | | | 0000343 | 8 | |
| メジャー | | 2017-10-05 | Pgpool log is empty after upgrade |
| | | | 0000344 | 1 | |
| マイナー | 完了 | 2017-10-05 | pgpool doesn't start with multiple listen_addresses |
| | | | 0000345 | 24 | 5 |
| メジャー | | 2017-11-07 | pgpool node.js prepared statement |
| | | | 0000347 | 4 | |
| システム停止 | | 2017-10-10 | backend response with kind 'E' when expecting 'R' |
| | | | 0000348 | 1 | 1 |
| メジャー | | 2017-11-09 | pgpool failover scenario ERROR - pgpool 3.6.6 (postgres 9.3.5) |
| | | | 0000350 | 3 | |
| メジャー | | 2017-10-10 | pcp_proc_info: error while loading shared libraries: libpcp.so.1: cannot open shared object file: No such file or directory |
| | | | 0000351 | 2 | |
| クラッシュ | | 2017-12-08 | pgpool crashes after a network outage to the master |
| | | | 0000353 | 11 | 3 |
| システム停止 | | 2017-10-27 | Once slave is attached the master becomes very slow and evantully hangs |
| | | | 0000354 | 5 | 1 |
| システム停止 | | 2017-10-24 | No ReadyForQuery packet after an erroneous prepared statement |
| | | | 0000355 | 3 | 1 |
| マイナー | | 2017-10-18 | SELECT queries are not load balanced after a commit (when using extended queries) |
| | | | 0000356 | 2 | |
| メジャー | | 2017-11-09 | pg_terminate_backend() causing failover despite setting flag |
| | | | 0000357 | 4 | |
| マイナー | | 2017-10-25 | Memcached status for different sessions is inconsistent |
| | | | 0000358 | 1 | |
| マイナー | | 2017-10-25 | Spelling error in a config file example of a tutorial page |
| | | | 0000359 | 3 | |
| システム停止 | | 2017-10-25 | invalid PCP packet, incorrect packet length, could not connect to pcp on port 9898 |
| | | | 0000360 | 3 | |
| マイナー | | 2017-12-08 | log_statement does not work with extended protocol |
| | | | 0000361 | 6 | 2 |
| マイナー | | 2017-11-29 | Can't detach node from pgpoolAdmin UI, while pcp_detach_node works fine |
| | | | 0000362 | 5 | |
| マイナー | | 2017-11-08 | pg_terminate_backend() causes failover when run as non-super user |
| | | | 0000363 | 2 | 2 |
| 微調整 | | 2017-11-09 | health check not detect node after down |
| | | | 0000364 | 10 | 4 |
| システム停止 | | 2018-06-17 | PGPool hangs when then number of connections are greater than num_init_children |
| | | | 0000365 | 3 | 1 |
| マイナー | 完了 | 2017-11-23 | PGpool for EDB advanced server role always standby |
| | | | 0000366 | 12 | 2 |
| メジャー | 完了 | 2017-12-22 | failed: FATAL: failed to read kind from backend |
| | | | 0000367 | 2 | |
| システム停止 | | 2017-11-23 | Manual failover with Pgpool and repmgr |
| | | | 0000368 | 4 | 1 |
| マイナー | | 2017-12-08 | show pool_nodes from client-node and pgpool-node different? |
| | | | 0000369 | 2 | |
| マイナー | | 2017-11-28 | yum's baseurl does not exist and it can not be used |
| | | | 0000370 | 13 | 1 |
| システム停止 | | 2018-02-16 | Pgpool get stuck with db exception followed by select |
| | | | 0000371 | 3 | 4 |
| マイナー | | 2017-12-19 | specify per node health check parameters setting in pgpool-II 3.7.0 does not work |
| | | | 0000372 | 3 | |
| マイナー | 完了 | 2017-12-27 | can not purge cached query with multiple |
| | | | 0000374 | 4 | |
| メジャー | | 2018-02-16 | md5 authentication is broken |
| | | | 0000375 | 4 | |
| マイナー | | 2018-05-01 | extended query error |
| | | | 0000376 | 15 | 7 |
| マイナー | | 2018-01-24 | child process was terminated by segmentation fault |
| | | | 0000377 | 6 | 4 |
| メジャー | | 2018-01-18 | Getting stuck on waiting on wrong backend for kind |
| | | | 0000378 | 4 | |
| メジャー | | 2018-05-07 | Pgpool fails all connections when secondary goes down |
| | | | 0000379 | 18 | 3 |
| メジャー | | 2018-04-06 | Many connections go into state 'idle in transaction' |
| | | | 0000380 | 3 | 1 |
| メジャー | | 2018-02-17 | When a node is down, the first query to the cluster fails |
| | | | 0000381 | 6 | |
| システム停止 | | 2018-03-29 | Problem when recovery attempts starting a fallen node |
| | | | 0000382 | 4 | 2 |
| クラッシュ | 完了 | 2018-04-06 | Pgpool fails to start with a watchdog error |
| | | | 0000383 | 6 | 1 |
| メジャー | | 2018-05-22 | Child process used to much memory, memory leak |
| | | | 0000384 | 3 | 1 |
| メジャー | 解決済 | 2018-03-14 | Pool worker children uses random primary_node_id when in master_slave replication |
| | | | 0000386 | 2 | 2 |
| クラッシュ | | 2018-05-01 | Pgpool fails to start with a watchdog error |
| | | | 0000387 | 2 | |
| マイナー | 完了 | 2018-04-06 | pgpool-II 3.6.1 child process remain waiting for a non-existing client socket to send queries |
| | | | 0000388 | 2 | |
| マイナー | | 2018-06-13 | pgpool-II 3.6.1 child process remain waiting for a non-existing client socket to send queries |
| | | | 0000391 | 4 | 1 |
| マイナー | | 2018-04-18 | no response from pcp_detach_node with -g option |
| | | | 0000392 | | 1 |
| メジャー | | 2019-01-30 | PGpool master lost connection to database even if the other services and pgpool slave didn't lost connecton. |
| | | | 0000393 | 3 | |
| メジャー | 完了 | 2018-04-27 | When multiple failover happens the pgpool pool node status is going into standby -stanby state |
| | | | 0000394 | 4 | |
| メジャー | | 2018-05-07 | When multiple failover happens the pgpool pool node status is going into standby -stanby state |
| | | | 0000395 | 4 | 1 |
| クラッシュ | | 2018-06-04 | Degenerate backend request for node_id: 0 |
| | | | 0000396 | 19 | 4 |
| メジャー | | 2020-02-18 | pgpool is getting started but not able to connect using port 9999 using psql application |
| | | | 0000397 | | |
| クラッシュ | | 2019-01-30 | Watchdog lifecheck seldom failure |
| | | | 0000398 | | |
| メジャー | | 2019-01-30 | useful logs are not displayed - no matter what config level for logs is used |
| | | | 0000399 | 2 | 1 |
| メジャー | | 2018-05-21 | Pgpool-II always regards '%P' as 0 even when primary node id = 1 down occurs failover |
| | | | 0000400 | 4 | |
| マイナー | | 2018-06-04 | RPM conflict libmemcached in pgpool37 and pgdg10 repo |
| | | | 0000401 | 4 | |
| 微調整 | 解決済 | 2018-06-04 | PCP commands requesting a password even with .pcppass file |
| | | | 0000402 | 3 | 2 |
| クラッシュ | 完了 | 2018-06-04 | write on backend 0 failed with error :"Success" |
| | | | 0000403 | 13 | 2 |
| クラッシュ | | 2018-11-15 | About : 0000402: write on backend 0 failed with error :"Success" |
| | | | 0000404 | 3 | 1 |
| クラッシュ | 完了 | 2018-06-20 | segmentation fault after failover |
| | | | 0000405 | 3 | |
| メジャー | | 2018-08-06 | ERROR: unable to read message length DETAIL: message length (8) in slot 1 does not match with slot 0(12) bash-4.1$ |
| | | | 0000406 | 10 | 1 |
| マイナー | | 2018-08-06 | failover called with old-primary = -1 |
| | | | 0000407 | 8 | 2 |
| マイナー | 解決済 | 2018-06-25 | health check process doesn't start in some cases |
| | | | 0000408 | 14 | 3 |
| メジャー | | 2018-08-06 | Connection hangs in DISCARD mode on the backend server |
| | | | 0000409 | 1 | 1 |
| マイナー | | 2018-07-23 | worker process is not restarted after failover on standby pgpool with in watchdog cluster |
| | | | 0000410 | 7 | |
| メジャー | | 2019-04-04 | Session is closed abnormally when reading tables to whose schema the user doesn't have privilege |
| | | | 0000411 | 12 | 3 |
| メジャー | | 2018-10-20 | Disable authentication in PgPool |
| | | | 0000412 | 2 | |
| メジャー | 完了 | 2018-08-20 | Not able to configure pgpool in AWS with elastic IP |
| | | | 0000413 | 7 | 2 |
| マイナー | 完了 | 2018-08-20 | watchdog issues |
| | | | 0000414 | 1 | 2 |
| メジャー | 完了 | 2018-12-04 | pg_dump causes Segmentation fault (core dumped) |
| | | | 0000415 | 9 | 3 |
| メジャー | | 2019-01-30 | 0000414: pg_dump causes Segmentation fault (core dumped) |
| | | | 0000416 | 2 | |
| メジャー | 完了 | 2018-08-27 | Detaching standby with load_balance_node=false causes application error: "ERROR: unable to read data from DB node 3" |
| | | | 0000417 | 2 | |
| メジャー | 完了 | 2018-08-27 | show pool_nodes is showing inconsistent roles(primary, standby) of postgresql nodes |
| | | | 0000418 | 8 | 3 |
| メジャー | | 2019-01-30 | pg_dumpall is exiting with coredump |
| | | | 0000419 | 12 | 3 |
| マイナー | | 2018-11-01 | pg_md5: -m removes users |
| | | | 0000420 | 5 | |
| マイナー | 完了 | 2018-08-14 | pg_md5 makes pgpool hang |
| | | | 0000421 | 5 | |
| メジャー | | 2018-08-11 | pgPool does not connect when Master node is down |
| | | | 0000422 | 5 | |
| マイナー | 完了 | 2019-01-30 | pg_md5: Add support for an user/password input file |
| | | | 0000423 | 5 | |
| マイナー | | 2018-08-16 | Connecting Pgpool-II during failback causes a possible hang |
| | | | 0000424 | 7 | |
| マイナー | | 2019-05-21 | pcp_recovery_nod in follow_master_command possibly fails with an error |
| | | | 0000425 | 2 | |
| マイナー | 解決済 | 2018-08-27 | pgpool_setup don't work with pre PostgreSQL 10. |
| | | | 0000426 | 1 | |
| メジャー | | 2018-09-14 | Pgpool-II contines to emit warning messages |
| | | | 0000427 | 1 | |
| マイナー | | 2018-09-11 | pg_enc emits wrong warnings |
| | | | 0000428 | 1 | |
| システム停止 | | 2018-09-05 | Secure TCP/IP Connections with SSL does not work any more |
| | | | 0000429 | 3 | 1 |
| メジャー | 完了 | 2018-09-18 | FATAL: Add to watchdog cluster request is rejected by node |
| | | | 0000431 | 5 | |
| マイナー | | 2018-10-16 | In native replication mode, online-recovery is blocked after a child process exits abnormally while accepting a connection. |
| | | | 0000432 | 4 | 4 |
| マイナー | | 2018-10-17 | Received resultset tuples, but no field structure for them exception in JDBC |
| | | | 0000433 | 2 | |
| マイナー | | 2018-10-19 | IN (SELECT ...) can not be rewritten in native replication mode |
| | | | 0000434 | 3 | 1 |
| マイナー | | 2018-10-23 | Segmentation fault due to a query error and Sync messages in native replication mode |
| | | | 0000435 | 15 | 5 |
| システム停止 | | 2018-10-24 | Unexpected movement on load balancing (master slave mode) |
| | | | 0000436 | 4 | 4 |
| メジャー | | 2018-11-20 | when a long session with a massive of db operation, the child pgpool process consume too much cpu resource |
| | | | 0000438 | 5 | 5 |
| マイナー | | 2018-11-20 | Memory consumption |
| | | | 0000439 | 2 | |
| メジャー | | 2018-12-04 | EOF detected while reading pid file |
| | | | 0000440 | 2 | |
| メジャー | 解決済 | 2018-11-02 | pool_nodes status |
| | | | 0000441 | 1 | |
| マイナー | | 2018-11-20 | Could not receive data from client: Connection reset by peer. |
| | | | 0000443 | 5 | 1 |
| メジャー | | 2018-11-19 | Segmentation fault occurs when a certain Bind message is sent in native replication mode. |
| | | | 0000444 | 7 | 2 |
| マイナー | | 2018-11-26 | pgpool does not take into account parameters order in startup packet |
| | | | 0000445 | 18 | 16 |
| メジャー | | 2018-11-27 | failover fail when I hold on connection with the port of pgpool-II ,9999 |
| | | | 0000446 | 13 | 2 |
| メジャー | | 2018-11-23 | show pool_nodes; reports both nodes as standby |
| | | | 0000447 | 9 | 2 |
| メジャー | | 2018-12-04 | connection expired problem |
| | | | 0000448 | 4 | 1 |
| メジャー | | 2018-12-06 | pgpool holds the connections as idle_in_transaction which are timed out due to idle_in_transaction setting on backend nodes |
| | | | 0000449 | 2 | |
| メジャー | | 2018-12-07 | Standby status recovery |
| | | | 0000450 | 1 | |
| マイナー | | 2019-01-30 | PDF generation appears to be broken |
| | | | 0000451 | 4 | 2 |
| マイナー | | 2018-12-26 | pgpool can only detect backend_hostname0 after failover switch |
| | | | 0000452 | 2 | |
| メジャー | | 2019-01-10 | Child process exits with status 6 by signal 6 |
| | | | 0000453 | 1 | |
| 些細 | | 2019-01-03 | There is an error in the explanation of logdir. |
| | | | 0000454 | 2 | 4 |
| 要望 | | 2019-02-18 | When multiple failover happens the pgpool pool node status is going into standby -stanby state |
| | | | 0000455 | 7 | 3 |
| マイナー | | 2019-01-21 | watchdog lifecheck process has segfalut in query mode |
| | | | 0000456 | 9 | |
| メジャー | | 2019-02-18 | Error in `pgpool: dw_ies ies_db 10.247.202.70(56024) idle': free(): invalid next size (fast): 0x000000000143ffc0 |
| | | | 0000457 | 2 | |
| 要望 | | 2019-01-29 | White_function_list |
| | | | 0000458 | 14 | 2 |
| メジャー | | 2019-02-27 | Pgpool generates lot of core dump files |
| | | | 0000459 | 4 | 2 |
| メジャー | 完了 | 2019-01-27 | pgpool sending deletes to standby |
| | | | 0000461 | 2 | |
| 要望 | | 2019-02-04 | white and black function list parameters |
| | | | 0000462 | 12 | 4 |
| メジャー | | 2019-02-07 | ERROR: invalid memory alloc request size 1073742608 |
| | | | 0000463 | 6 | |
| マイナー | | 2019-02-07 | Missing WARN for single server setups |
| | | | 0000464 | 2 | 1 |
| マイナー | | 2019-03-11 | pool_passwd with md5 / DETAIL: username "pgpcheck" has invalid password type: 2 |
| | | | 0000465 | 8 | 1 |
| メジャー | | 2019-03-05 | pgpool cannot accept new connections while attached backend stream-wal replicated dbslave:tcp:5432 unreachable |
| | | | 0000466 | 1 | 1 |
| システム停止 | | 2019-05-21 | Pgpool with RDS Aurora Postgres - prepared statement "_PLAN0x80fb40000" does not exist] |
| | | | 0000467 | 18 | 4 |
| メジャー | | 2019-08-14 | Encoding issue with bytea field and PostgreSQL 11 |
| | | | 0000468 | 12 | 6 |
| メジャー | | 2019-04-02 | When doing a query using cursor, a memory leak happens |
| | | | 0000469 | 4 | |
| メジャー | | 2019-03-21 | LOG ERROR: primary 0 owns only 0 standbys out of 1 |
| | | | 0000470 | 1 | |
| メジャー | | 2019-08-13 | Make install fails |
| | | | 0000471 | 4 | |
| メジャー | | 2019-03-13 | pcp_watchdog_info alternatives missing or wrong |
| | | | 0000472 | 3 | 1 |
| メジャー | | 2019-05-21 | error where running java application and error in pgpool-ii crror log |
| | | | 0000473 | 2 | |
| メジャー | | 2019-05-21 | pgPool no starting up post system reboot |
| | | | 0000474 | 3 | 1 |
| メジャー | | 2019-05-21 | pgpool goes to restarting loop after receiving failover request |
| | | | 0000475 | 12 | 2 |
| メジャー | | 2019-03-21 | pcp_recovery_node command hangs while recovering standby and standby not being shown up in show pool_nodes; |
| | | | 0000476 | 20 | 2 |
| メジャー | | 2019-04-05 | Pgpool Master and Slaves are not properly sync the backends DB status..Pool Mater and Slaves are showing fault backend status.. |
| | | | 0000477 | 1 | |
| システム停止 | 完了 | 2019-05-21 | backend databases continue to report waiting |
| | | | 0000478 | 7 | 3 |
| マイナー | | 2019-05-21 | pcp_proc_count authentication failed |
| | | | 0000480 | 4 | |
| マイナー | | 2019-08-26 | FATAL: unable to read data from DB node 0 Detail: EOF encountered with backend. |
| | | | 0000481 | 2 | 2 |
| メジャー | | 2019-05-21 | a race condition causing a segfault in replication mode. |
| | | | 0000482 | 2 | |
| マイナー | | 2019-05-21 | Segfault when failback occurs during executing the query. |
| | | | 0000483 | 5 | 1 |
| マイナー | | 2019-08-15 | online-recovery is blocked after a child process exits abnormally with replication mode and watchdog |
| | | | 0000484 | 6 | |
| メジャー | | 2019-04-02 | Change node status withount change role type |
| | | | 0000485 | 1 | |
| マイナー | | 2019-04-03 | Log duration of queries |
| | | | 0000486 | 6 | 2 |
| メジャー | | 2019-05-21 | segfaults at drop database |
| | | | 0000487 | 4 | 1 |
| メジャー | | 2019-05-21 | As a user, Not able to connect psql with pgpool port after server restart |
| | | | 0000488 | 10 | 1 |
| システム停止 | | 2019-05-04 | write on backend 0 failed with error :"Success" - pgpool:3.7.8 |
| | | | 0000489 | 3 | |
| マイナー | | 2019-04-04 | Not able generate log for syslog destinatio |
| | | | 0000490 | 9 | |
| クラッシュ | | 2019-08-13 | Child process was terminated after receiving `SYNC` message |
| | | | 0000491 | 3 | |
| メジャー | | 2019-04-09 | MD5 Authentication doesn't work as expected in RAW mode with more than 1 backends |
| | | | 0000492 | 9 | 2 |
| マイナー | | 2019-04-09 | pgpool sending SET schema 'Owner'; to primary node only |
| | | | 0000493 | 2 | 1 |
| マイナー | | 2019-04-10 | when read old pgpool_status file, wrong variable was referenced by Pgpool-II. |
| | | | 0000494 | 3 | |
| マイナー | | 2019-04-15 | While connection through ODBC , show pool_nodes from client is also going to backend nodes instead of getting excuted in pgpool |
| | | | 0000495 | 4 | |
| メジャー | 完了 | 2019-04-15 | Need suggestion for latest stable version 4.0.2 or 4.0.4? |
| | | | 0000497 | 5 | 1 |
| マイナー | | 2019-08-15 | FATAL: failed to read kind from backend |
| | | | 0000498 | 4 | |
| マイナー | 完了 | 2019-04-17 | PGPOOL and Aurora generating huge amount of logs |
| | | | 0000499 | 5 | |
| マイナー | | 2019-04-19 | Connection to PGPool-II Fails to return results in case of error |
| | | | 0000501 | 5 | 4 |
| メジャー | | 2020-02-25 | password authentication failed for user "postgres" in 3.7.9 |
| | | | 0000502 | 1 | |
| マイナー | | 2019-05-17 | Load is not working distributing properly between Master and Slave |
| | | | 0000503 | 4 | 3 |
| クラッシュ | | 2019-08-15 | 2019-04-28 09:43:14: pid 26332: WARNING: child process with pid: 26387 was terminated by segmentation fault |
| | | | 0000504 | 1 | 1 |
| メジャー | | 2019-05-21 | Getting error during failover. Failover script is not running properly. |
| | | | 0000505 | 4 | |
| クラッシュ | | 2019-06-03 | coredump |
| | | | 0000506 | 3 | 2 |
| メジャー | 完了 | 2019-05-17 | FATAL: pgpool is not accepting any new connections |
| | | | 0000507 | 3 | 1 |
| メジャー | | 2019-05-17 | show pool_nodes |
| | | | 0000508 | 13 | 2 |
| メジャー | | 2020-02-25 | received degenerate backend request for node_id: 0 write on backend 0 failed with error :"Success" |
| | | | 0000509 | 2 | |
| マイナー | | 2019-05-21 | pgpool-II HA |
| | | | 0000510 | 1 | |
| メジャー | 完了 | 2019-05-17 | pcp_recovery_node fails: node id 1 is not valid |
| | | | 0000511 | 6 | |
| クラッシュ | | 2019-05-20 | PG Pool is initiating more than (max_pool * num_init_children connections) + super_user_connections when PG slave is coming UP |
| | | | 0000512 | 2 | 1 |
| メジャー | | 2019-08-16 | V4_0_5 doesn't compile under freebsd on auth/pool_hba.c |
| | | | 0000513 | 5 | 2 |
| マイナー | | 2019-07-02 | pgpool showing primary node down even if it is UP. |
| | | | 0000514 | 10 | 1 |
| メジャー | | 2019-05-23 | verify_backend_node_status: there's no primary node |
| | | | 0000515 | 6 | |
| メジャー | | 2019-08-15 | Pgpool node status waiting |
| | | | 0000516 | 1 | |
| メジャー | | 2020-05-21 | ping probes fail with long hostnames due to small buffer |
| | | | 0000517 | 1 | |
| メジャー | | 2019-05-23 | Healthcheck not starting for new node after reloading configuration |
| | | | 0000518 | 1 | |
| マイナー | | 2019-05-23 | Questions on using connection pooling |
| | | | 0000519 | 3 | 1 |
| マイナー | | 2019-08-16 | Freebsd build is failing |
| | | | 0000520 | 11 | |
| マイナー | | 2019-06-26 | Encountering - psql: ERROR: connection cache is full HINT: increase max_pool |
| | | | 0000521 | 8 | |
| マイナー | | 2019-06-18 | In streaming replication mode, load balancing mode on, load balancing happens only for executing queries not for db connections. |
| | | | 0000522 | 6 | |
| マイナー | | 2019-09-17 | Error :EOF encountered with frontend |
| | | | 0000524 | 4 | 1 |
| マイナー | | 2019-08-13 | pgpool performance issue |
| | | | 0000525 | 12 | 8 |
| メジャー | | 2019-08-15 | Segmentation fault occurs when memory_cache_enable is set to on |
| | | | 0000526 | 6 | 3 |
| マイナー | | 2019-07-23 | pgpool authentication |
| | | | 0000527 | 2 | |
| マイナー | | 2019-07-10 | Not able to post question on pgpool-general@pgpool.net |
| | | | 0000528 | 30 | 14 |
| メジャー | | 2019-07-24 | pgpool authentication for cached connection |
| | | | 0000529 | 3 | |
| メジャー | | 2019-07-17 | Load test |
| | | | 0000530 | 7 | 1 |
| メジャー | | 2019-10-07 | pgpool can't connect to standby replica |
| | | | 0000531 | 21 | 3 |
| マイナー | | 2019-09-11 | FATAL: unable to bind occurs |
| | | | 0000532 | 6 | |
| マイナー | | 2020-02-25 | pgpool log not showing proper info |
| | | | 0000533 | 3 | 1 |
| メジャー | | 2020-02-25 | Pgpooll - standby.stop appear instantly despite i configure it to be delayed |
| | | | 0000534 | 8 | 2 |
| メジャー | | 2020-02-18 | unable to connect when enable_pool_hba is off and pg_hba on password |
| | | | 0000535 | 6 | |
| メジャー | | 2019-08-27 | Frequently seeing "unable to flush data to frontend" errors and timeout errors in application servers |
| | | | 0000536 | 5 | 1 |
| マイナー | | 2020-04-14 | Recovery of standby node in streaming replication mode causes all connections to be dropped |
| | | | 0000537 | 4 | 2 |
| メジャー | | 2019-08-26 | pgpool no longer executing if_down_cmd on shutdown |
| | | | 0000538 | 10 | |
| マイナー | | 2019-08-16 | Unable to load balance selects on primary and standby |
| | | | 0000539 | 2 | 5 |
| クラッシュ | | 2019-09-02 | Random segfault crashes of pgpool |
| | | | 0000540 | 5 | |
| 些細 | | 2020-02-03 | pcp_recovey_node authentication failed for user "pgpool" |
| | | | 0000541 | 11 | |
| 要望 | | 2019-09-06 | Unable to start Virtual IP for Pgpool |
| | | | 0000542 | 4 | 2 |
| メジャー | | 2020-04-14 | pgpool service will not come up after failover |
| | | | 0000543 | 2 | |
| メジャー | 完了 | 2019-09-06 | VIP unable to switch to another PGPOOL |
| | | | 0000544 | 7 | |
| メジャー | | 2019-09-18 | standby_postgres is in quarantine status |
| | | | 0000545 | 35 | 19 |
| メジャー | | 2019-10-31 | Quorum lost and not recovered |
| | | | 0000546 | 10 | 4 |
| システム停止 | | 2019-10-31 | Executing
DML & DDL combination via PostgresSQL ODBC to pgpool fails with
'WARNING: child process with pid: 24870 was terminated |
| | | | 0000547 | 20 | 7 |
| メジャー | | 2019-10-31 | We need to do arping again after recovering from split-brain. |
| | | | 0000548 | 6 | 2 |
| マイナー | | 2019-12-24 | syslog_facility couldn't be changed by reload |
| | | | 0000549 | 2 | 1 |
| メジャー | | 2019-10-16 | Pgpool doesn't release virtual IP when we stop Postgres service in one node |
| | | | 0000550 | 2 | 4 |
| マイナー | | 2019-10-16 | Pgpool system queries |
| | | | 0000551 | 11 | 2 |
| マイナー | | 2020-03-06 | Some cases where now() is not rewritten in native replication mode |
| | | | 0000552 | 21 | 2 |
| メジャー | | 2019-10-30 | unable to read data from DB node 0 and "write on backend 0 failed with error :"Success"" |
| | | | 0000553 | 1 | |
| マイナー | 解決済 | 2019-10-29 | transaction mode in pgpool |
| | | | 0000554 | 5 | 1 |
| マイナー | | 2019-10-21 | stale socket files after system crash |
| | | | 0000555 | 4 | 2 |
| システム停止 | 解決済 | 2019-11-05 | pgpool does not start without any notice even in debug mode |
| | | | 0000556 | 6 | 1 |
| マイナー | | 2019-12-13 | Leaking sessions on pg backend. |
| | | | 0000557 | 6 | |
| マイナー | | 2020-04-14 | Syslog settings ignored |
| | | | 0000558 | 6 | |
| メジャー | | 2019-11-28 | Watchdog Mode unable to attach Virtual IP after any PgPool Node goes down |
| | | | 0000559 | 8 | 4 |
| メジャー | | 2020-04-14 | Randomly closed connections |
| | | | 0000560 | 7 | |
| 要望 | | 2019-12-10 | allow to whitelist caching the results of stable functions |
| | | | 0000561 | 16 | 2 |
| マイナー | | 2019-12-10 | why transaction with 'set' statement would always be marked as 'writing transaction', even it is began with 'read only'? |
| | | | 0000562 | 5 | 3 |
| メジャー | | 2020-04-14 | Add to watchdog cluster request is rejected by node 9000 |
| | | | 0000563 | 3 | 3 |
| クラッシュ | 完了 | 2020-01-16 | PGPool genera error y cierra la conexión cuando hay error en el master |
| | | | 0000564 | 5 | 6 |
| クラッシュ | | 2020-01-20 | PGPool generates error and close the conection where there is an error in the master |
| | | | 0000565 | 3 | 1 |
| マイナー | | 2020-03-06 | Segmentation falut happend by worker process |
| | | | 0000566 | 5 | 1 |
| マイナー | | 2020-02-03 | Pgpool is not failing over compeltely to First node when 2nd and 3rd nodes were down |
| | | | 0000567 | 4 | 1 |
| マイナー | | 2020-02-03 | Getting belwo error while bring ing up pgpool and my VIP is not coming up |
| | | | 0000568 | 14 | |
| メジャー | | 2020-03-24 | Reattaching detached primary doesn't bring it up |
| | | | 0000569 | 3 | |
| メジャー | | 2020-02-03 | pgpool-II-4.1.0 can not log messages on syslog |
| | | | 0000570 | 5 | |
| マイナー | 完了 | 2020-04-14 | Log rotation is not working |
| | | | 0000571 | 7 | 1 |
| マイナー | | 2020-03-06 | child process segfault after reload |
| | | | 0000572 | 3 | |
| メジャー | | 2021-03-26 | ERROR: unable to read message kind. DETAIL: kind does not match between |
| | | | 0000573 | 15 | 8 |
| クラッシュ | | 2020-03-06 | LISTEN/NOTIFY no longer completely work after 4.1.0 upgrade (C# Npgsql) |
| | | | 0000574 | 3 | |
| メジャー | | 2020-01-13 | waiting for the quorum to start escalation process |
| | | | 0000575 | 4 | 1 |
| システム停止 | | 2020-01-29 | cannot bring streaming slave online |
| | | | 0000576 | 8 | 6 |
| 些細 | | 2020-01-19 | getsockopt() detected error "Connection refused" |
| | | | 0000577 | 113 | 17 |
| メジャー | | 2020-03-02 | PGPOOLII goes unstable after DB fail over |
| | | | 0000578 | 1 | 1 |
| メジャー | | 2020-04-14 | 4.1: Cannot get standby online after a pcp_promote_node, instead getting "... failed to start in 90 second" |
| | | | 0000579 | 2 | |
| メジャー | | 2020-04-14 | 4.1: BUG: Follow_master_command parameter mismatch |
| | | | 0000580 | 2 | |
| メジャー | | 2020-04-14 | 4.1: BUG: Pgpool_recovery extension protocol has two more parameters |
| | | | 0000581 | 2 | 2 |
| マイナー | | 2020-01-30 | Pgpool release VIP |
| | | | 0000582 | 8 | |
| メジャー | | 2020-04-16 | 'idle in transaction' connections in pgpool server and not able see the same in postgres servers |
| | | | 0000583 | 6 | 2 |
| メジャー | | 2020-04-14 | pcp_recovery_node return "unable to connect to master node" |
| | | | 0000584 | 3 | |
| マイナー | | 2020-04-14 | Watchdog session disconnected when any node disconnected (even the standby) |
| | | | 0000585 | 2 | |
| メジャー | | 2020-04-14 | Can't connect to virtual ip (VIP) on cluster node |
| | | | 0000586 | 6 | |
| マイナー | | 2020-04-14 | Do not update status of slave host on PGPool |
| | | | 0000587 | 1 | |
| メジャー | 完了 | 2020-02-28 | pcp_detach_node命令没有按照配置的pcp_socket_dir去寻找.s.PGSQL.9898文件 |
| | | | 0000588 | 2 | 5 |
| メジャー | | 2020-04-14 | I cant stop/promtye backend node ( master or salve) from pgpooladmin |
| | | | 0000589 | 1 | |
| マイナー | 完了 | 2020-02-28 | command ' pcp_detach_node ' cant find the socket file follow the config dir in pgpool.conf |
| | | | 0000590 | 3 | 2 |
| メジャー | | 2020-03-02 | sonarqube uses jdbc driver to connect to pgpool-II failed |
| | | | 0000591 | 6 | 3 |
| メジャー | | 2020-03-06 | pgpoo stuck under a large amount of concurrency |
| | | | 0000592 | 2 | |
| メジャー | | 2020-03-06 | postgres 12 clustering using pgpool : unable to use password-less login |
| | | | 0000594 | 11 | 1 |
| メジャー | | 2020-04-14 | Problem on Connection Pooling |
| | | | 0000595 | 4 | 1 |
| マイナー | | 2020-05-21 | Incorrect message length validation in do_SCRAM() - backend authentication |
| | | | 0000596 | 3 | 1 |
| マイナー | | 2020-05-21 | Problems in watchdog processing json data |
| | | | 0000597 | 8 | 9 |
| メジャー | | 2022-02-03 | pgpool2 fails to run the if_down_cmd and arping_cmd |
| | | | 0000598 | 11 | 5 |
| マイナー | | 2020-05-21 | segmentation fault |
| | | | 0000599 | 4 | 1 |
| メジャー | | 2020-04-02 | Fortinet discards lots of TCP packets with reason: Not a Valid SYN Packet |
| | | | 0000600 | 9 | 1 |
| マイナー | | 2020-04-13 | Pgpool ii Node status 'waiting' |
| | | | 0000601 | 6 | 1 |
| メジャー | | 2020-04-14 | Some SQL queries are missed |
| | | | 0000602 | 3 | |
| マイナー | | 2020-04-20 | sr_health_check authentication fails with any other password type than cleartext password |
| | | | 0000605 | 7 | |
| 微調整 | | 2020-04-21 | Shared memcache for multiple pgpool instances |
| | | | 0000606 | 6 | |
| 微調整 | | 2020-05-01 | Log spam from successful authentication |
| | | | 0000607 | 3 | |
| 微調整 | | 2020-05-18 | Executing Procedures containing DML on primary node only |
| | | | 0000608 | 2 | 2 |
| メジャー | | 2020-05-21 | pgpool ssl front end accept all ciphers. not working as expected. |
| | | | 0000609 | 3 | 2 |
| メジャー | | 2020-05-01 | server closed the connection unexpectedly |
| | | | 0000611 | 5 | 3 |
| クラッシュ | | 2020-05-15 | segmentation fault |
| | | | 0000612 | 2 | |
| メジャー | | 2020-05-12 | Getting connection error when I tried to connect with tcp port |
| | | | 0000613 | 2 | |
| マイナー | | 2020-05-15 | segfault, error 4 in libc-2.28.so, when using 'enable_pool_hba' |
| | | | 0000614 | 2 | 1 |
| クラッシュ | | 2020-08-24 | Invalid memory reference in sync_backend_from_watchdog() |
| | | | 0000615 | 17 | 9 |
| マイナー | | 2020-08-24 | Issue with replication type of connection from client side |
| | | | 0000616 | 15 | 2 |
| メジャー | | 2024-07-21 | sorry, too many clients already |
| | | | 0000617 | 5 | 2 |
| マイナー | | 2020-06-24 | Loadbalancer ambiguous nature after restoring old master |
| | | | 0000618 | 8 | 2 |
| マイナー | | 2020-06-21 | Loadbalancer behaving not expectedly with hibernate and Hikari |
| | | | 0000619 | 1 | 1 |
| マイナー | | 2020-08-24 | Regression test 055.backend_all_down fails if PG_INSTALL_DIR is not set to "/usr/local/pgsql/bin" (the default value) |
| | | | 0000620 | 4 | 6 |
| システム停止 | | 2020-08-26 | Problem with promote server |
| | | | 0000621 | 5 | |
| システム停止 | | 2020-09-01 | pgpool does not start beacuse of "failed to create INET domain socket" error message |
| | | | 0000622 | 9 | 2 |
| メジャー | | 2020-09-01 | wd_escalation_command script not called when master pgpool shutdown |
| | | | 0000623 | 5 | |
| マイナー | | 2020-09-14 | Show pool_nodes not showing full data |
| | | | 0000624 | 21 | 8 |
| メジャー | | 2020-08-07 | pcp_recovery_node reports: postmaster on hostname:"/var/run/postgresql" database:"template1" user:"postgres" failed to start ... |
| | | | 0000625 | 8 | 6 |
| マイナー | | 2020-08-26 | Proces/service pgpool |
| | | | 0000626 | 5 | |
| マイナー | | 2020-08-26 | PCP_PROMOTE_NODE |
| | | | 0000627 | 2 | |
| メジャー | | 2020-10-07 | Master and slave not able to connect each other to perform health check for few mints intermittently |
| | | | 0000628 | 2 | 1 |
| マイナー | 完了 | 2020-08-10 | pgpool activities not recording in pgppol.log instead writing in messages |
| | | | 0000629 | 2 | |
| メジャー | 完了 | 2020-08-10 | pgpool activities not recording in pgppol.log instead writing in messages |
| | | | 0000630 | 3 | 1 |
| メジャー | | 2020-09-10 | pgpool activities not recording in pgppol.log instead writing in messages |
| | | | 0000631 | 3 | |
| マイナー | | 2020-09-14 | pgpool activities not recording in pgppol.log |
| | | | 0000632 | 7 | 3 |
| クラッシュ | | 2020-08-20 | FATAL: Failed to set caps on main pgpool process |
| | | | 0000633 | 8 | |
| マイナー | | 2020-08-24 | Getting random, but frequent "failed to unlock semaphore" errors |
| | | | 0000634 | 1 | |
| マイナー | | 2020-08-18 | Until pgpool determines that the standby node is down, the query to the cluster fails |
| | | | 0000635 | 7 | 2 |
| システム停止 | | 2020-08-20 | Cannot startup standby in watchdog mode |
| | | | 0000636 | 11 | |
| メジャー | | 2020-08-24 | pgpool failover not working |
| | | | 0000637 | 4 | 2 |
| メジャー | | 2020-10-07 | Unable to read the data from frontend |
| | | | 0000638 | 1 | |
| メジャー | | 2020-08-21 | authentication failed for user "pgpool" |
| | | | 0000639 | 9 | |
| マイナー | | 2020-10-08 | Confused by wd_escalation_command and failover_command |
| | | | 0000640 | 5 | |
| マイナー | | 2020-09-12 | How to put pgpgool2 in "maintenance mode"? |
| | | | 0000641 | 3 | |
| メジャー | | 2020-08-28 | Too much memory consumption by Pgpool |
| | | | 0000642 | 3 | |
| メジャー | | 2020-08-27 | Replication slot |
| | | | 0000643 | 12 | 3 |
| メジャー | | 2020-08-31 | message length (24) in slot 2 does not match with slot 0(25) |
| | | | 0000644 | 1 | |
| 微調整 | | 2020-08-29 | Log spam when using shared memory cache |
| | | | 0000645 | 4 | |
| マイナー | | 2020-08-31 | Pgpool memory consumption when increasing the log level |
| | | | 0000646 | 5 | 1 |
| メジャー | | 2020-09-14 | After kill the primary failover not works and if i turn on again the prymary i have 3 standby |
| | | | 0000647 | 2 | |
| マイナー | | 2020-10-30 | How to find application and system ip of the connection from pgpool |
| | | | 0000648 | 5 | |
| メジャー | | 2020-09-16 | Looks pgpool is not taking the configuration of pool_passwd after password change |
| | | | 0000649 | 3 | 5 |
| メジャー | | 2020-12-09 | Add to watchdog cluster request is rejected by node "master:9000" |
| | | | 0000650 | 3 | |
| マイナー | | 2020-09-28 | Information request on pgpool-II |
| | | | 0000651 | 5 | |
| メジャー | | 2020-11-20 | pgpool stops suddenly |
| | | | 0000652 | | |
| マイナー | | 2020-10-09 | Non-posix headers are not cross-platform compatible. |
| | | | 0000653 | | 1 |
| メジャー | 完了 | 2020-10-15 | hostname displaying wrong information on show pool_nodes for the node2 |
| | | | 0000654 | 5 | |
| システム停止 | | 2020-11-19 | pool_send_and_wait: Error or notice message from backend: message: "syntax error at or near "DO"" |
| | | | 0000655 | 1 | |
| メジャー | | 2020-10-29 | pgpool drops connections |
| | | | 0000656 | 4 | 2 |
| メジャー | | 2020-11-19 | Child connection counter issue if query cancelled |
| | | | 0000657 | 4 | |
| メジャー | | 2020-11-25 | Sporadic "Sorry, to many clients already" |
| | | | 0000658 | 4 | 6 |
| メジャー | | 2020-12-02 | LOST node cannot rejoin cluster due to life-check |
| | | | 0000659 | 3 | |
| マイナー | | 2020-12-22 | Failover issue in replication mode |
| | | | 0000661 | 5 | |
| 要望 | | 2020-12-09 | connecting to Application with Virtual IP |
| | | | 0000662 | 3 | |
| メジャー | 完了 | 2020-11-30 | PgPool with WatchDog Cluster doesn't work after reboot all the machines |
| | | | 0000663 | | |
| マイナー | 完了 | 2020-11-30 | test |
| | | | 0000664 | 6 | |
| メジャー | | 2020-12-10 | PgPool with WatchDog Cluster doesn't work after reboot all the machines |
| | | | 0000665 | 3 | |
| マイナー | | 2020-12-02 | pcp_attach_node is looking fro wrong directory |
| | | | 0000666 | 10 | 1 |
| マイナー | | 2020-12-04 | Restoring standby nodes in streaming replication mode causes discarding all connections (DETAIL: failover or failback Event dete |
| | | | 0000667 | 1 | |
| マイナー | | 2020-12-03 | The patch version 4.1.5 path change changed and underscore was introduced. |
| | | | 0000668 | 3 | 5 |
| メジャー | | 2020-12-09 | Virtual IP not starting up due to failed to create watchdog heartbeat receive socket |
| | | | 0000669 | 4 | |
| メジャー | | 2020-12-10 | Watchdog escalation failed to acquire delegate IP |
| | | | 0000670 | 3 | |
| マイナー | | 2020-12-09 | 4.2 Compilation Fails on FreeBSD |
| | | | 0000672 | 12 | 5 |
| メジャー | | 2021-02-19 | Child connection counter issue after the primary node reattached (switch back from secondary) |
| | | | 0000673 | 3 | |
| クラッシュ | | 2020-12-21 | cannot change into new db by using pgpool |
| | | | 0000674 | 1 | |
| システム停止 | | 2020-12-16 | the slave have local db but different from pgpool |
| | | | 0000675 | 4 | |
| メジャー | 完了 | 2020-12-23 | PgPool shutdown backends incorrectly, when node 0 fails |
| | | | 0000676 | 21 | 6 |
| メジャー | | 2021-01-06 | ERROR: unable to flush data to frontend |
| | | | 0000677 | 6 | |
| マイナー | | 2021-01-11 | In replication mode, the number of retrieved records is not correct after inserting data into the foreign table. |
| | | | 0000678 | 2 | |
| マイナー | | 2021-03-30 | In replication mode, after inserting data into the foreign table, delete or update will cause the operation to wait. |
| | | | 0000679 | 1 | |
| メジャー | | 2021-01-04 | 自动踢出集群 |
| | | | 0000681 | 3 | 2 |
| メジャー | | 2021-01-04 | Pgpool and query "copy" |
| | | | 0000683 | 6 | 5 |
| クラッシュ | | 2023-11-17 | Application couldn't connect to Postgres DB via pgpool |
| | | | 0000684 | 1 | 3 |
| マイナー | | 2023-04-14 | The standby status of pcp_watchdog_info isn't changed from "LOADING", after rebooting a standby server. |
| | | | 0000686 | 4 | 1 |
| メジャー | | 2021-01-26 | load balance invalid |
| | | | 0000687 | 4 | |
| マイナー | | 2021-02-19 | wrong pg_rewind usage in follow_primary.sh.sample |
| | | | 0000688 | 2 | |
| メジャー | 完了 | 2021-02-13 | pgpool not going to connect database after db restart. |
| | | | 0000689 | 4 | |
| メジャー | | 2021-06-15 | master node and virtual ip not assigned |
| | | | 0000690 | 7 | |
| メジャー | | 2021-11-04 | standby still refer to oldprimary after oldprimary down |
| | | | 0000691 | | 1 |
| メジャー | | 2021-02-15 | Split brain problem with wathdog |
| | | | 0000692 | 12 | |
| メジャー | | 2021-02-18 | Data is not replicated after bring back master to life |
| | | | 0000693 | 2 | 1 |
| メジャー | | 2021-06-15 | Getting segfaults errors frequently |
| | | | 0000694 | 2 | |
| マイナー | | 2021-05-20 | follow_primary.sh.sample should create a replication slot after running pg_rewind |
| | | | 0000695 | 7 | 1 |
| メジャー | | 2021-03-20 | pgpool not caching connection |
| | | | 0000696 | 8 | 2 |
| メジャー | | 2021-06-15 | pgpool connection caching issue |
| | | | 0000697 | 4 | 1 |
| マイナー | | 2021-04-08 | auto_failback never triggers |
| | | | 0000698 | 5 | |
| システム停止 | | 2021-03-21 | pgpool chile process keep getting re created |
| | | | 0000699 | 6 | 1 |
| メジャー | | 2021-06-15 | SCRAM authentication failed for username having more than 32 characters |
| | | | 0000700 | 16 | 9 |
| メジャー | | 2021-05-20 | Pgpool child process with pid: XXXXX was terminated by segmentation fault |
| | | | 0000701 | 8 | 3 |
| メジャー | | 2021-04-17 | Password auth not working with md5 |
| | | | 0000702 | 4 | 1 |
| メジャー | | 2021-04-19 | Standby node in streaming replication is considered lagging while it's not, all requests sent to it return NULL values |
| | | | 0000705 | 5 | |
| メジャー | | 2021-06-08 | last primary DB on PGPool |
| | | | 0000706 | 2 | |
| メジャー | 完了 | 2021-05-11 | update pgpooladmin |
| | | | 0000707 | 2 | 1 |
| マイナー | | 2021-05-20 | Statment level load-balancing breaks redirect preferences |
| | | | 0000708 | 3 | |
| 要望 | | 2022-06-28 | Unable to setup LDAP Client Authentication using pgpool-II |
| | | | 0000709 | | 1 |
| クラッシュ | | 2021-05-07 | segfault while triggering failover command |
| | | | 0000710 | 2 | |
| 要望 | 完了 | 2021-06-08 | No se realiza el failover del servidor PostgreSQL |
| | | | 0000711 | 5 | 7 |
| メジャー | 新規 | 2021-05-24 | APPARENT DEADLOCK!!! Complete Status: Managed Threads: 3 Active Threads: 3 |
| | | | 0000712 | 6 | |
| メジャー | | 2022-06-28 | DETAIL: kind does not match between master(52) slot[1] (45) |
| | | | 0000713 | 13 | |
| メジャー | | 2021-06-22 | PgPool HA in Kubernetes |
| | | | 0000715 | 7 | 1 |
| メジャー | | 2021-06-22 | PgPool Loadbalancer in Kubernetes |
| | | | 0000716 | 3 | |
| メジャー | 完了 | 2022-06-28 | Master/Slave out of sync (pgpool2) |
| | | | 0000717 | 6 | |
| メジャー | | 2021-07-19 | pgpool-II-pg96-extensions.x86_64 missing files |
| | | | 0000718 | 6 | 3 |
| メジャー | | 2021-07-19 | Problem with status watchdog |
| | | | 0000719 | 3 | |
| マイナー | 完了 | 2021-07-01 | pg_terminate_backend stop all backends when it is used over pgpool psql session |
| | | | 0000720 | 7 | 5 |
| マイナー | | 2021-07-12 | Connection timed out for node of cluster |
| | | | 0000721 | 6 | 4 |
| メジャー | | 2022-06-28 | cpu load high frequently |
| | | | 0000722 | 2 | |
| マイナー | | 2022-06-28 | Wanted to know how to monitor backup and restore progress in postgresql |
| | | | 0000723 | 2 | 4 |
| マイナー | | 2022-06-28 | when start pgpool,it appears error |
| | | | 0000724 | 2 | |
| マイナー | | 2022-06-28 | when start pgpool,it appears error |
| | | | 0000725 | 3 | |
| メジャー | | 2021-08-02 | SSL connectivity to pgpool fails |
| | | | 0000726 | 14 | 1 |
| メジャー | | 2022-06-28 | postmaster on DB node 0 was shutdown by administrative command |
| | | | 0000727 | 3 | |
| メジャー | 完了 | 2021-08-05 | Yum repository might be broken |
| | | | 0000728 | 3 | |
| マイナー | | 2022-06-28 | duplicate backend_flag |
| | | | 0000729 | 9 | 2 |
| メジャー | | 2022-01-20 | Failover was not triggered |
| | | | 0000730 | 5 | |
| メジャー | | 2021-08-23 | postgresql Primary server down，Virtual IP cannot be switched |
| | | | 0000731 | 1 | 1 |
| システム停止 | | 2021-09-14 | Fails to execute follow_primary_command in Pgpool-II 4.2.4 |
| | | | 0000732 | 5 | 1 |
| メジャー | | 2021-12-07 | Segmentation fault at failover in standby only streaming_replication mode. |
| | | | 0000734 | 3 | 1 |
| メジャー | 完了 | 2021-10-27 | PgPool is not working in manual repmgr switch-over |
| | | | 0000735 | | |
| マイナー | 新規 | 2021-10-26 | pgpool start "*** buffer overflow detected ***: pgpool: watchdog terminated" |
| | | | 0000736 | 1 | |
| メジャー | 完了 | 2022-06-28 | pgpool连接azure postgre主从集群启动报错 |
| | | | 0000737 | 3 | |
| メジャー | | 2022-02-05 | failed to authenticate |
| | | | 0000738 | 4 | 1 |
| メジャー | | 2021-11-17 | stop primary PostgreSQL server, the virtual IP is not released |
| | | | 0000739 | 3 | |
| 要望 | | 2021-11-22 | pgpool should report the number of backend connections in use per child process |
| | | | 0000740 | 17 | 1 |
| メジャー | | 2022-05-23 | ssl_ciphers are not honored and pgpool port allow other vulnerable non-compliant ciphers as per sslscan tool |
| | | | 0000741 | 6 | |
| マイナー | | 2022-06-28 | Conflict file when install Pgpool-II in CentOS 7 |
| | | | 0000742 | 2 | 2 |
| メジャー | | 2022-02-22 | Long time failover |
| | | | 0000743 | 3 | |
| メジャー | | 2022-06-28 | Enabling pgpool service to start automatically as documentation with Health Check set cause issues when rebooting |
| | | | 0000744 | 5 | 3 |
| メジャー | | 2022-06-28 | child process with pid: 20263 was terminated by segmentation fault |
| | | | 0000745 | 6 | 3 |
| マイナー | | 2022-06-28 | Application giving jdbc connection error while high load |
| | | | 0000746 | 9 | |
| メジャー | | 2022-06-28 | Getting below error in pgpool log on salve server. Need your help to find the reason of it. |
| | | | 0000748 | 5 | 1 |
| マイナー | | 2022-06-28 | pgpool udp heartbeat with another randomly port. |
| | | | 0000749 | 5 | 1 |
| クラッシュ | | 2022-06-28 | Hi dear, I am testing fileover on a 2 node cluster by downloading the primary server. When I upload the services again I see in |
| | | | 0000750 | 7 | 4 |
| メジャー | | 2022-10-24 | child process with pid: 22220 was terminated by segmentation fault |
| | | | 0000751 | 5 | |
| マイナー | | 2022-06-02 | Why does pgpool lock in SSL on server start? |
| | | | 0000752 | 3 | |
| メジャー | | 2022-06-28 | Connection to database goes to hand due to auto failover |
| | | | 0000753 | 10 | |
| メジャー | | 2022-06-03 | Disconnection issue of pgpool server to database node |
| | | | 0000754 | 3 | |
| マイナー | | 2022-06-28 | Object not in prerequisite state: 7 ERROR: currval of sequence error |
| | | | 0000755 | 3 | |
| 些細 | | 2022-06-16 | pgpool.conf.sample-replication の log_filename の設定値誤り |
| | | | 0000756 | 1 | |
| マイナー | | 2022-06-16 | invalid length of startup packet |
| | | | 0000757 | 7 | 3 |
| マイナー | | 2022-08-18 | pgpool_setup does not work well with PG15b1 |
| | | | 0000758 | 1 | |
| マイナー | | 2022-06-26 | Mixed SQL construction causes PgPool "show pool_*" forwarding to backend |
| | | | 0000759 | 3 | |
| システム停止 | 完了 | 2022-06-30 | pcp_attach_node gives a successful output, however fails to actually attach |
| | | | 0000760 | 5 | |
| メジャー | | 2022-08-01 | With 1 primary + 2 standby's w/ streaming replication, PGPool does not down 2nd standby on failover |
| | | | 0000761 | 4 | 1 |
| メジャー | 完了 | 2022-07-27 | Hi Team,I am getting the error.Please guide on this |
| | | | 0000762 | 6 | |
| 些細 | | 2022-08-01 | use so_reuseport in pgpool child process |
| | | | 0000763 | 8 | |
| メジャー | | 2022-08-19 | help troubleshooting verify_backend_node_status: primary 0 owns only 0 standbys out of 2 |
| | | | 0000764 | 2 | |
| マイナー | | 2022-08-16 | Connection hang when using asyncpg |
| | | | 0000765 | 5 | 3 |
| メジャー | | 2022-08-27 | Certain workers become degenerate with SSL_read errors |
| | | | 0000766 | 2 | |
| 些細 | | 2022-12-26 | Pgpool-IIのRPMを用いてのリグレッションテストが失敗する |
| | | | 0000767 | 3 | |
| メジャー | | 2022-09-27 | Official Pgpool Docker Image Doesn't Come With PCP? |
| | | | 0000768 | 1 | |
| マイナー | | 2022-09-29 | Pgpool auto_failback not working |
| | | | 0000769 | 2 | 4 |
| メジャー | | 2022-10-11 | Pgpool will not run if_cmd_down command |
| | | | 0000770 | 4 | |
| マイナー | 新規 | 2023-01-19 | kind mismatch among backends, kind details are: 0[2] 1[Z] 2[Z] messages for very simple SELECTs |
| | | | 0000771 | 8 | |
| メジャー | 新規 | 2022-11-01 | Unable to connect pgpool port 9999 using newly created users and database |
| | | | 0000772 | 23 | |
| 微調整 | | 2022-12-13 | all backend node server reboot |
| | | | 0000773 | 3 | |
| マイナー | | 2023-01-20 | status 256 in log |
| | | | 0000774 | 5 | |
| マイナー | | 2022-12-13 | node info Status "waiting" that never ends |
| | | | 0000775 | 2 | |
| マイナー | | 2022-12-26 | Spammed with "new IPC connection received" from watchdog |
| | | | 0000776 | 5 | 5 |
| マイナー | | 2022-12-13 | Could you please share pgpool 4.3.3 and postgresql-14 configuration files |
| | | | 0000777 | 7 | 1 |
| メジャー | | 2023-01-06 | PgPool unable to connect to Aurora Postgresql |
| | | | 0000778 | 1 | |
| メジャー | | 2023-01-04 | Installation failure on Centos stream 8 with PG-12 |
| | | | 0000779 | 2 | |
| メジャー | 完了 | 2023-01-06 | Pgpool certification |
| | | | 0000780 | 110 | 6 |
| メジャー | | 2023-06-21 | pool_send_and_wait: Error or notice message from backend |
| | | | 0000781 | 1 | |
| マイナー | | 2023-01-31 | Auto_failback |
| | | | 0000782 | 1 | |
| メジャー | | 2023-01-31 | RPM Installation failed on Centos Stream 9 with postgres 15 |
| | | | 0000783 | 1 | |
| クラッシュ | | 2023-02-10 | "CREATE EXTENSION pgpool_recovery" failed. |
| | | | 0000784 | 1 | |
| メジャー | | 2023-02-10 | How to make pgpool-II extension work with postgresql-contrib together? |
| | | | 0000785 | 2 | |
| メジャー | | 2023-02-13 | psql can't found $libdir/pgpool-recovery |
| | | | 0000786 | 5 | |
| メジャー | | 2023-03-09 | ERROR: pid xxxx: AES encryption is not supported by this build |
| | | | 0000787 | 6 | |
| マイナー | | 2023-03-02 | PCP unix socket path does not match the configuration |
| | | | 0000788 | 1 | |
| メジャー | | 2023-03-02 | pgpool can't access /var/run directory to open pid file and create watchdog command server socket after reboot |
| | | | 0000789 | 16 | 5 |
| メジャー | | 2023-04-05 | pgpool-II 请求阻塞 |
| | | | 0000790 | 1 | |
| マイナー | | 2023-05-22 | compile error with musl |
| | | | 0000791 | 8 | 4 |
| マイナー | | 2023-03-30 | master watchdog has performed failover. but both node-0 (standby) and node-1 (primary) still alive. |
| | | | 0000792 | 10 | |
| マイナー | | 2023-03-27 | The read_only_function_list and write_function_list configurations cannot coexist |
| | | | 0000794 | 5 | 1 |
| 些細 | | 2023-05-06 | why prepare statement always send to primary node? |
| | | | 0000795 | 7 | 4 |
| メジャー | | 2023-06-14 | invalid memory alloc request size 18446744073709551592 |
| | | | 0000797 | 9 | 8 |
| マイナー | | 2023-04-26 | pgpool 4.3.5 found app=sr_check_worker WARNING: failed to unlock semaphore |
| | | | 0000798 | 8 | 4 |
| マイナー | | 2023-05-22 | when the load_balancing_node is delay too much, a writing function call will send to standby? |
| | | | 0000799 | 5 | 2 |
| マイナー | | 2023-05-16 | health_check_period and health_check_max_retries parameters not respected consitently |
| | | | 0000800 | 4 | 1 |
| メジャー | | 2023-05-20 | pcp_watchdog_info check connection failed with error "Connection refused" |
| | | | 0000801 | 4 | |
| メジャー | | 2023-06-19 | show pool_nodes role column not getting updated on postgres faiover |
| | | | 0000802 | 2 | |
| マイナー | | 2023-06-19 | pcp_recovery_node without password fails |
| | | | 0000803 | 7 | 2 |
| システム停止 | | 2024-06-12 | Pgpool will not connect to RDS Postgres via RDS Proxy |
| | | | 0000804 | 1 | |
| メジャー | 完了 | 2023-08-17 | Performance issuies |
| | | | 0000805 | 3 | |
| メジャー | 完了 | 2023-07-03 | I'm trying to create a mega cluster of 6 nodes with postgresql-12 and pgpoll- ii, it fails when I include node 5 and 5 |
| | | | 0000806 | 1 | |
| マイナー | | 2023-08-17 | lots of logs pool_pending_message_set_flush_request with level LOG |
| | | | 0000807 | 4 | 1 |
| クラッシュ | | 2023-08-17 | Child process crashes when backend sends a protocol v2 errorMessage |
| | | | 0000808 | 3 | |
| マイナー | | 2023-08-26 | I need to know which table PostgreSQL 12 stores the information from to generate the "show pool_nodes" report |
| | | | 0000809 | 2 | 5 |
| メジャー | | 2025-02-06 | Pgpool hang with broken pipe write error when the connection is established and idle for about 2-3 hours. |
| | | | 0000810 | 1 | |
| 要望 | フィードバック | 2023-09-01 | Pgpool-II 4.4.4 on other operating systems than centos 7.9? |
| | | | 0000811 | 3 | |
| クラッシュ | | 2023-09-15 | pgpool[141977]: segfault at 14 ip 000000000043532e sp 00007ffd11099370 error 6 in pgpool[400000+21a000] |
| | | | 0000812 | 2 | 11 |
| マイナー | | 2023-09-27 | failed to connect to PostgreSQL server on "customerdb-a:5432", getsockopt() failed |
| | | | 0000813 | 2 | 2 |
| メジャー | | 2023-10-03 | invalid degenerate backend request, node id : 0 status: [3] is not valid for failover |
| | | | 0000816 | 1 | |
| マイナー | 新規 | 2023-11-02 | pgpool-II 4.3 relationship with postgresql-12 and archive_cleanup_command off the primary PostgreSQL system |
| | | | 0000817 | | 5 |
| メジャー | | 2023-11-14 | watchdog choice as a leader a node with less wd_priority |
| | | | 0000818 | 1 | |
| マイナー | | 2023-11-27 | pgpool generate warn mesage Unable to parse the query |
| | | | 0000819 | | |
| マイナー | | 2023-11-27 | pcp_node_info not in sync with pg_stat_replication |
| | | | 0000821 | 3 | |
| マイナー | | 2023-12-14 | show pool_nodes showing node as a standby of pg_role and role |
| | | | 0000823 | 15 | 3 |
| メジャー | | 2024-06-11 | Watchdog dies and kills pgpool2 when network gets shortly interrupted |
| | | | 0000824 | 3 | |
| メジャー | | 2024-01-04 | pgpoll 4.5 on Rocky linux 9, metadata expiration check: -1 day, 17:50:46 Aug on Fri 29 Dec 2023 02:21:22 AM CET |
| | | | 0000825 | 4 | |
| マイナー | | 2024-02-06 | Auto Failover and Recovery options |
| | | | 0000826 | 1 | |
| メジャー | | 2024-01-25 | When the first node (node with id 0) is not primary, pcp is not starting |
| | | | 0000827 | 2 | |
| マイナー | 新規 | 2024-02-01 | pcp commands doesn't work with delegated IP |
| | | | 0000828 | 11 | 1 |
| メジャー | | 2024-02-27 | PgPool doesnt perform load balancing of RW queries after switchover of postgreSQL database nodes |
| | | | 0000829 | | 2 |
| マイナー | | 2024-03-07 | pgpool2 fails to build with -Werror=implicit-function-declaration |
| | | | 0000830 | 8 | |
| マイナー | 新規 | 2024-03-07 | build failure for snprintf.c |
| | | | 0000831 | 1 | |
| クラッシュ | 新規 | 2024-03-12 | Getting "unable to read data from DB node 0" when new primary attached to pgpool after failover |
| | | | 0000832 | 3 | |
| システム停止 | 完了 | 2024-04-05 | pcp_node_info command command failed with reason: "ArraySize" |
