| | | | 0000809 | 2 | 5 |
| major | | 2025-02-06 | Pgpool hang with broken pipe write error when the connection is established and idle for about 2-3 hours. |
| | | | 0000616 | 15 | 2 |
| major | | 2024-07-21 | sorry, too many clients already |
| | | | 0000803 | 7 | 2 |
| block | | 2024-06-12 | Pgpool will not connect to RDS Postgres via RDS Proxy |
| | | | 0000823 | 15 | 3 |
| major | | 2024-06-11 | Watchdog dies and kills pgpool2 when network gets shortly interrupted |
| | | | 0000831 | 1 | |
| crash | new | 2024-03-12 | Getting "unable to read data from DB node 0" when new primary attached to pgpool after failover |
| | | | 0000829 | | 2 |
| minor | | 2024-03-07 | pgpool2 fails to build with -Werror=implicit-function-declaration |
| | | | 0000830 | 8 | |
| minor | new | 2024-03-07 | build failure for snprintf.c |
| | | | 0000828 | 11 | 1 |
| major | | 2024-02-27 | PgPool doesnt perform load balancing of RW queries after switchover of postgreSQL database nodes |
| | | | 0000825 | 4 | |
| minor | | 2024-02-06 | Auto Failover and Recovery options |
| | | | 0000827 | 2 | |
| minor | new | 2024-02-01 | pcp commands doesn't work with delegated IP |
| | | | 0000826 | 1 | |
| major | | 2024-01-25 | When the first node (node with id 0) is not primary, pcp is not starting |
| | | | 0000821 | 3 | |
| minor | | 2023-12-14 | show pool_nodes showing node as a standby of pg_role and role |
| | | | 0000818 | 1 | |
| minor | | 2023-11-27 | pgpool generate warn mesage Unable to parse the query |
| | | | 0000819 | | |
| minor | | 2023-11-27 | pcp_node_info not in sync with pg_stat_replication |
| | | | 0000683 | 6 | 5 |
| crash | | 2023-11-17 | Application couldn't connect to Postgres DB via pgpool |
| | | | 0000817 | | 5 |
| major | | 2023-11-14 | watchdog choice as a leader a node with less wd_priority |
| | | | 0000816 | 1 | |
| minor | new | 2023-11-02 | pgpool-II 4.3 relationship with postgresql-12 and archive_cleanup_command off the primary PostgreSQL system |
| | | | 0000813 | 2 | 2 |
| major | | 2023-10-03 | invalid degenerate backend request, node id : 0 status: [3] is not valid for failover |
| | | | 0000812 | 2 | 11 |
| minor | | 2023-09-27 | failed to connect to PostgreSQL server on "customerdb-a:5432", getsockopt() failed |
| | | | 0000126 | 5 | 2 |
| crash | | 2023-09-25 | pgpool get stuck after failover |
| | | | 0000811 | 3 | |
| crash | | 2023-09-15 | pgpool[141977]: segfault at 14 ip 000000000043532e sp 00007ffd11099370 error 6 in pgpool[400000+21a000] |
| | | | 0000810 | 1 | |
| feature | feedback | 2023-09-01 | Pgpool-II 4.4.4 on other operating systems than centos 7.9? |
| | | | 0000780 | 110 | 6 |
| major | | 2023-06-21 | pool_send_and_wait: Error or notice message from backend |
| | | | 0000802 | 2 | |
| minor | | 2023-06-19 | pcp_recovery_node without password fails |
| | | | 0000801 | 4 | |
| major | | 2023-06-19 | show pool_nodes role column not getting updated on postgres faiover |
| | | | 0000795 | 7 | 4 |
| major | | 2023-06-14 | invalid memory alloc request size 18446744073709551592 |
| | | | 0000800 | 4 | 1 |
| major | | 2023-05-20 | pcp_watchdog_info check connection failed with error "Connection refused" |
| | | | 0000799 | 5 | 2 |
| minor | | 2023-05-16 | health_check_period and health_check_max_retries parameters not respected consitently |
| | | | 0000794 | 5 | 1 |
| trivial | | 2023-05-06 | why prepare statement always send to primary node? |
| | | | 0000797 | 9 | 8 |
| minor | | 2023-04-26 | pgpool 4.3.5 found app=sr_check_worker WARNING: failed to unlock semaphore |
| | | | 0000789 | 16 | 5 |
| major | | 2023-04-05 | pgpool-II 请求阻塞 |
| | | | 0000791 | 8 | 4 |
| minor | | 2023-03-30 | master watchdog has performed failover. but both node-0 (standby) and node-1 (primary) still alive. |
| | | | 0000792 | 10 | |
| minor | | 2023-03-27 | The read_only_function_list and write_function_list configurations cannot coexist |
| | | | 0000786 | 5 | |
| major | | 2023-03-09 | ERROR: pid xxxx: AES encryption is not supported by this build |
| | | | 0000788 | 1 | |
| major | | 2023-03-02 | pgpool can't access /var/run directory to open pid file and create watchdog command server socket after reboot |
| | | | 0000785 | 2 | |
| major | | 2023-02-13 | psql can't found $libdir/pgpool-recovery |
| | | | 0000784 | 1 | |
| major | | 2023-02-10 | How to make pgpool-II extension work with postgresql-contrib together? |
| | | | 0000783 | 1 | |
| crash | | 2023-02-10 | "CREATE EXTENSION pgpool_recovery" failed. |
| | | | 0000782 | 1 | |
| major | | 2023-01-31 | RPM Installation failed on Centos Stream 9 with postgres 15 |
| | | | 0000781 | 1 | |
| minor | | 2023-01-31 | Auto_failback |
| | | | 0000770 | 4 | |
| minor | new | 2023-01-19 | kind mismatch among backends, kind details are: 0[2] 1[Z] 2[Z] messages for very simple SELECTs |
| | | | 0000778 | 1 | |
| major | | 2023-01-04 | Installation failure on Centos stream 8 with PG-12 |
| | | | 0000772 | 23 | |
| tweak | | 2022-12-13 | all backend node server reboot |
| | | | 0000774 | 5 | |
| minor | | 2022-12-13 | node info Status "waiting" that never ends |
| | | | 0000776 | 5 | 5 |
| minor | | 2022-12-13 | Could you please share pgpool 4.3.3 and postgresql-14 configuration files |
| | | | 0000771 | 8 | |
| major | new | 2022-11-01 | Unable to connect pgpool port 9999 using newly created users and database |
| | | | 0000750 | 7 | 4 |
| major | | 2022-10-24 | child process with pid: 22220 was terminated by segmentation fault |
| | | | 0000769 | 2 | 4 |
| major | | 2022-10-11 | Pgpool will not run if_cmd_down command |
| | | | 0000768 | 1 | |
| minor | | 2022-09-29 | Pgpool auto_failback not working |
| | | | 0000765 | 5 | 3 |
| major | | 2022-08-27 | Certain workers become degenerate with SSL_read errors |
