[pgpool-hackers: 978] pgpool-II 3.4.3, 3.3.7, 3.2.12, 3.1.15, and 3.0.19 released
Yugo Nagata
nagata at sraoss.co.jp
Fri Jul 24 17:14:54 JST 2015
Hi,
Pgpool Global Development Group is pleased to announce the availability
of pgpool-II 3.4.3, 3.3.7, 3.2.12, 3.1.15, and 3.0,19. 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.4.3 (tataraboshi) 2015/07/24
* Version 3.4.3
This is a bugfix release against pgpool-II 3.4.2.
__________________________________________________________________
* Bug fixes
- Fix "cannot find xlog functions" error in pgpool-recovery
(Muhammad Usama)
The argument data type of PostgreSQL's pg_xlogfile_name() function
has been changed from text to pg_lsn since PostgreSQL 9.4. And
pgpool-recovery was still trying to locate the function by old
signature.
- Fix problem with memory cache invalidation (Muhammad Usama)
The internal buffer for storing the table oids needs to be homed in
long living memory context as it has to survive throughout the child
life.
See [pgpool-general: 3643] for details.
- Pass empty string parameters in failover command when pgpool-II
does not have a value for any particular parameter (Muhammad Usama)
Instead of omitting the values for the parameters when pgpool-II does
not have any value for a particular parameter, it now passes an empty
string to the failover command. This makes sure that failover script
will always receive the exact number of expected parameters.
- pgpool-II should use the local definition of snprintf functions only
if they are not provided by OS (Muhammad Usama)
- Add debug info to show how much shared memory is allocated
(Tatsuo Ishii)
- Downgrading the error level for EOF on backend connection for main
process (Muhammad Usama)
Throwing the FATAL error when EOF is encountered with backend is very
harsh in pgpool main process and can cause undesirable behavior.
Downgrading it to simple ERROR.
- doc: Clarify load balancing condition (Tatsuo Ishii)
- doc: Clarify description of pcp_promote_node (Tatsuo Ishii)
It does not actually promote PostgreSQL standby.
- doc: Fix outdated limitation description about load balancing using
JDBC driver (Tatsuo Ishii)
Even if autocommit is false, load balancing is possible in certain
conditions.
- Fix a misplaced code which makes a log code unreachable and rephrase
the log message (Muhammad Usama)
- Fix a problem in elog.c when forwarding a message to frontend clients
(Muhammad Usama)
Error while forwarding the message to the frontend client can
potentially cause the infinite recursion and terminate the child with
ERRORDATA_STACK_SIZE exceeded error.
Fix is to check the recursion depth of send_message_to_frontend()
function and pulling the plug if it is more than two levels deep.
- Fix "select() system call interrupted" error (Tatsuo Ishii)
The health check process complains above and then:
ERROR: failed to make persistent db connection
DETAIL: connection to host:"x.x.x.x:5432 failed
However, the healthchek triggers neither fail over nor retrying. So,
except the annoying messages above, everything goes well. This could
occur more easily if 1) num_init_children is big and 2) pgpool
children go into idle state (no query arrived from client for
child_life_time seconds).
Original bug report is [pgpool-general: 3756] Connection Interrupted.
Patch created by Tatsuo Ishii. Enhancement from Usama.
- Fix the case when user table includes spaces (Tatsuo Ishii)
For example if table names including spaces are used, pgpool-II cannot
be handled correctly by the internal functions which access system
catalogs and it results in SQL errors. Solution is, to always use
delimited identifier.
Per bug #136.
http://www.pgpool.net/mantisbt/view.php?id=136
Also see [pgpool-general: 3818].
- Allow to use in-memory query cache size more than 4GB (Tatsuo Ishii)
This should have been allowed since in memory query cache was born.
- Do not send a query for checking insert lock in non replication mode
with extended query (Tatsuo Ishii)
- Save pgpool_status to disk each time when it is changed
(Tatsuo Ishii)
Previously, pgpool-II saves pgpool_status file when pgpool-II
explicitly is going shutdown. This is fine in most cases and it saves
slight CPU cycles. But if pgpool-II killed abnormally or the system
forces pgpool-II to go down by OOM killer, next pgpool-II restarting
could load obsolete status file.
===============================================================================
3.3.7 (tokakiboshi) 2015/07/24
* Version 3.3.7
This is a bugfix release against pgpool-II 3.3.6.
__________________________________________________________________
* Bug fixes
- Fix "cannot find xlog functions" error in pgpool-recovery
(Muhammad Usama)
The argument data type of PostgreSQL's pg_xlogfile_name() function
has been changed from text to pg_lsn since PostgreSQL 9.4. And
pgpool-recovery was still trying to locate the function by old
signature.
- Pass empty string parameters in failover command when pgpool-II
does not have a value for any particular parameter (Muhammad Usama)
Instead of omitting the values for the parameters when pgpool-II does
not have any value for a particular parameter, it now passes an empty
string to the failover command. This makes sure that failover script
will always receive the exact number of expected parameters.
- doc: Clarify load balancing condition (Tatsuo Ishii)
- doc: Clarify description of pcp_promote_node (Tatsuo Ishii)
It does not actually promote PostgreSQL standby.
- doc: Fix outdated limitation description about load balancing using
JDBC driver (Tatsuo Ishii)
Even if autocommit is false, load balancing is possible in certain
conditions.
- Fix "select() system call interrupted" error (Tatsuo Ishii)
The health check process complains above and then:
ERROR: failed to make persistent db connection
DETAIL: connection to host:"x.x.x.x:5432 failed
However, the healthchek triggers neither fail over nor retrying. So,
except the annoying messages above, everything goes well. This could
occur more easily if 1) num_init_children is big and 2) pgpool
children go into idle state (no query arrived from client for
child_life_time seconds).
Original bug report is [pgpool-general: 3756] Connection Interrupted.
Patch created by Tatsuo Ishii. Enhancement from Usama.
- Fix the case when user table includes spaces (Tatsuo Ishii)
For example if table names including spaces are used, pgpool-II cannot
be handled correctly by the internal functions which access system
catalogs and it results in SQL errors. Solution is, to always use
delimited identifier.
Per bug #136.
http://www.pgpool.net/mantisbt/view.php?id=136
Also see [pgpool-general: 3818].
- Allow to use in-memory query cache size more than 4GB (Tatsuo Ishii)
This should have been allowed since in memory query cache was born.
- Do not send a query for checking insert lock in non replication mode
with extended query (Tatsuo Ishii)
===============================================================================
3.2.12 (namameboshi) 2015/07/24
* Version 3.2.12
This is a bugfix release against pgpool-II 3.2.11.
__________________________________________________________________
* Bug fixes
- Fix "cannot find xlog functions" error in pgpool-recovery
(Muhammad Usama)
The argument data type of PostgreSQL's pg_xlogfile_name() function
has been changed from text to pg_lsn since PostgreSQL 9.4. And
pgpool-recovery was still trying to locate the function by old
signature.
- Pass empty string parameters in failover command when pgpool-II
does not have a value for any particular parameter (Muhammad Usama)
Instead of omitting the values for the parameters when pgpool-II does
not have any value for a particular parameter, it now passes an empty
string to the failover command. This makes sure that failover script
will always receive the exact number of expected parameters.
- doc: Fix outdated limitation description about load balancing using
JDBC driver (Tatsuo Ishii)
Even if autocommit is false, load balancing is possible in certain
conditions.
- Allow to use in-memory query cache size more than 4GB (Tatsuo Ishii)
This should have been allowed since in memory query cache was born.
- Do not send a query for checking insert lock in non replication mode
with extended query (Tatsuo Ishii)
===============================================================================
3.1.15 (hatsuiboshi) 2015/07/24
* Version 3.1.15
This is a bugfix release against pgpool-II 3.1.14.
__________________________________________________________________
* Bug fixes
- Fix "cannot find xlog functions" error in pgpool-recovery
(Muhammad Usama)
The argument data type of PostgreSQL's pg_xlogfile_name() function
has been changed from text to pg_lsn since PostgreSQL 9.4. And
pgpool-recovery was still trying to locate the function by old
signature.
- Do not send a query for checking insert lock in non replication mode
with extended query (Tatsuo Ishii)
===============================================================================
3.0.19 (umiyameboshi) 2015/07/24
* Version 3.0.19
This is a bugfix release against pgpool-II 3.0.18.
__________________________________________________________________
* Bug fixes
- Fix "cannot find xlog functions" error in pgpool-recovery
(Muhammad Usama)
The argument data type of PostgreSQL's pg_xlogfile_name() function
has been changed from text to pg_lsn since PostgreSQL 9.4. And
pgpool-recovery was still trying to locate the function by old
signature.
- Do not send a query for checking insert lock in non replication mode
with extended query (Tatsuo Ishii)
===============================================================================
--
Yugo Nagata <nagata at sraoss.co.jp>
More information about the pgpool-hackers
mailing list