[pgpool-general: 4657] pgpool-II 3.5.2, 3.4.6, 3.3.10, 3.2.15, 3.1.18, and pgpoolAdmin 3.5.2 released
Bo Peng
pengbo at sraoss.co.jp
Tue Apr 26 17:33:59 JST 2016
Hi,
Pgpool Global Development Group is pleased to announce the availability
of pgpool-II 3.5.2, 3.4.6, 3.3.10, 3.2.15, 3.1.18, and pgpoolAdmin 3.5.2.
These are the latest stable minor versions of each major versions of pgpool-II.
You can download them from:
http://pgpool.net/mediawiki/index.php/Downloads
3.5.2 (ekieboshi) 2016/04/26
* Version 3.5.2
This is a bugfix release against pgpool-II 3.5.1.
__________________________________________________________________
* Bug fixes
- Fix for segfault during trusted_servers check (Muhammad Usama)
PostgreSQL's memory and exception manager APIs adopted by the
pgpool 3.4 are not thread safe and are causing the segmentation fault
in the watchdog lifecheck process, as it uses the threads to ping
configured trusted hosts for checking the upstream connections.
Fix is to remove threads and use the child process approach instead.
See [pgpool-general: 4569] for more details.
- Removing the limit on the maximum number of items in the
black_function_list and white_function_list lists. (Muhammad Usama)
extract_string_tokens in pool_config uses the fixed size malloc on
the array to hold the black_function_list/white_function_list items.
This imposes a limit of maximum items in these lists.
The fix is to use realloc to increase the array size when it gets full.
- Fix extended protocol hang with empty query (Tatsuo Ishii)
The fixes related to extended protocol cases in 3.5.1 broke the case
of empty query. In this case backend replies with "empty query
response" which is same meaning as a command complete message. Problem
is, when empty query response is received, pgpool does not reset the
query in progress flag thus keeps on waiting for backend. However,
backend will not send the ready for query message until it receives a
sync message. Fix is, resetting the in progress flag after receiving
the empty query response and reads from frontend expecting it sends a
sync message.
Per bug #190.
- Redirect all user queries to primary server (Tatsuo Ishii)
Up to now some user queries are sent to other than the primary server
even if load_balance_mode = off. This commit changes the behavior: if
load_balance_mode = off in streaming replication mode, now all the
user queries are sent to the primary server only.
Per bug #189.
- Change the PID length of pcp_proc_count command result to 6 characters
long (Bo Peng)
If the pgpool process ID are over 5 characters, the 6th character of each
process ID will be removed. This commit changes the process ID length of
pcp_proc_count command result to 6 characters long.
Per bug #188.
===============================================================================
3.4.6 (tataraboshi) 2016/04/26
* Version 3.4.6
This is a bugfix release against pgpool-II 3.4.5.
__________________________________________________________________
* Bug fixes
- Fix for segfault during trusted_servers check (Muhammad Usama)
PostgreSQL's memory and exception manager APIs adopted by the
pgpool 3.4 are not thread safe and are causing the segmentation fault
in the watchdog lifecheck process, as it uses the threads to ping
configured trusted hosts for checking the upstream connections.
Fix is to remove threads and use the child process approach instead.
See [pgpool-general: 4569] for more details.
- Removing the limit on the maximum number of items in the
black_function_list and white_function_list lists. (Muhammad Usama)
extract_string_tokens in pool_config uses the fixed size malloc on
the array to hold the black_function_list/white_function_list items.
This imposes a limit of maximum items in these lists.
The fix is to use realloc to increase the array size when it gets full.
- Redirect all user queries to primary server (Tatsuo Ishii)
Up to now some user queries are sent to other than the primary server
even if load_balance_mode = off. This commit changes the behavior: if
load_balance_mode = off in streaming replication mode, now all the
user queries are sent to the primary server only.
Per bug #189.
- Change the PID length of pcp_proc_count command result to 6 characters
long (Bo Peng)
If the pgpool process ID are over 5 characters, the 6th character of each
process ID will be removed. This commit changes the process ID length of
pcp_proc_count command result to 6 characters long.
Per bug #188.
===============================================================================
3.3.10 (tokakiboshi) 2016/04/26
* Version 3.3.10
This is a bugfix release against pgpool-II 3.3.9.
__________________________________________________________________
* Bug fixes
- Removing the limit on the maximum number of items in the
black_function_list and white_function_list lists. (Muhammad Usama)
extract_string_tokens in pool_config uses the fixed size malloc on
the array to hold the black_function_list/white_function_list items.
This imposes a limit of maximum items in these lists.
The fix is to use realloc to increase the array size when it gets full.
- Redirect all user queries to primary server (Tatsuo Ishii)
Up to now some user queries are sent to other than the primary server
even if load_balance_mode = off. This commit changes the behavior: if
load_balance_mode = off in streaming replication mode, now all the
user queries are sent to the primary server only.
Per bug #189.
- Change the PID length of pcp_proc_count command result to 6 characters
long (Bo Peng)
If the pgpool process ID are over 5 characters, the 6th character of each
process ID will be removed. This commit changes the process ID length of
pcp_proc_count command result to 6 characters long.
Per bug #188.
===============================================================================
3.2.15 (namameboshi) 2016/04/26
* Version 3.2.15
This is a bugfix release against pgpool-II 3.2.14.
__________________________________________________________________
* Bug fixes
- Removing the limit on the maximum number of items in the
black_function_list and white_function_list lists. (Muhammad Usama)
extract_string_tokens in pool_config uses the fixed size malloc on
the array to hold the black_function_list/white_function_list items.
This imposes a limit of maximum items in these lists.
The fix is to use realloc to increase the array size when it gets full.
- Redirect all user queries to primary server (Tatsuo Ishii)
Up to now some user queries are sent to other than the primary server
even if load_balance_mode = off. This commit changes the behavior: if
load_balance_mode = off in streaming replication mode, now all the
user queries are sent to the primary server only.
Per bug #189.
- Change the PID length of pcp_proc_count command result to 6 characters
long (Bo Peng)
If the pgpool process ID are over 5 characters, the 6th character of each
process ID will be removed. This commit changes the process ID length of
pcp_proc_count command result to 6 characters long.
Per bug #188.
===============================================================================
3.1.18 (hatsuiboshi) 2016/04/26
* Version 3.1.18
This is a bugfix release against pgpool-II 3.1.17.
__________________________________________________________________
* Bug fixes
- Removing the limit on the maximum number of items in the
black_function_list and white_function_list lists. (Muhammad Usama)
extract_string_tokens in pool_config uses the fixed size malloc on
the array to hold the black_function_list/white_function_list items.
This imposes a limit of maximum items in these lists.
The fix is to use realloc to increase the array size when it gets full.
- Redirect all user queries to primary server (Tatsuo Ishii)
Up to now some user queries are sent to other than the primary server
even if load_balance_mode = off. This commit changes the behavior: if
load_balance_mode = off in streaming replication mode, now all the
user queries are sent to the primary server only.
Per bug #189.
- Change the PID length of pcp_proc_count command result to 6 characters
long (Bo Peng)
If the pgpool process ID are over 5 characters, the 6th character of each
process ID will be removed. This commit changes the process ID length of
pcp_proc_count command result to 6 characters long.
Per bug #188.
===============================================================================
--
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan
More information about the pgpool-general
mailing list