[pgpool-general: 4612] pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, and pgpoolAdmin 3.5.1 released
Yugo Nagata
nagata at sraoss.co.jp
Mon Apr 4 23:45:33 JST 2016
Hi,
Pgpool Global Development Group is pleased to announce the availability
of pgpool-II 3.5.1, 3.4.5, 3.3.9, 3.2.14, 3.1.17, and pgpoolAdmin 3.5.1.
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.1 (ekieboshi) 2016/04/01
* Version 3.5.1
This is a bugfix release against pgpool-II 3.5.0.
__________________________________________________________________
* Bug fixes
- Add some warning messages for wd_authkey hash calculation failure
(Yugo Nagata)
Sometimes wd_authkey calculation fails for some reason other than
authkey mismatch. The additional messages make these distingushable
for each other.
- test: Fix regression test to check timeout of each test (Yugo Nagata)
- test: Allow timeout value to be specified by the command option
(Yugo Nagata)
- Fix compile issue on FreeBSD (Muhammad Usama)
Added missing include files.
Per bug #166. The patch is contributed by the bug reporter and
enhanced a little by Usama.
- test: Fix test/regression/clean.sh to remove binary files of
010.rewrite_timestamp test (Yugo Nagata)
- Fix memorry leak reported by Coverity (CID 1350095) (Yugo Nagata)
- Fixing pgpool-recovery module compilation issue with PostgreSQL 9.6
(Muhammad Usama)
Incorporating the change of function signature for GetConfigOption..()
functions in PostgreSQL 9.6.
- Fix to properly process an empty query that has only comments
(Tatsuo Ishii)
Pgpool-II recognized an empty query, for example "/* DBD::Pg ping test
v3.5.3 */" (note that it has no ';') as an error and emits message
"Unable to parse the query". This is because raw_parser() cannot
distinguish an empty query from an error query due to the poor API
design. To fix this new out parameter "*error" added to the
function. If an error occurred, the variable is set to true and caller
can know the reason why raw_parser() returns NIL is because of an error
query or an empty query.
Per bug #154. See [pgpool-hackers: 1359] for additional information.
- Fix a reset query stuck problem (Muhammad Usama)
The solution is to report FRONTEND_ERROR instead of simple ERROR when
pool_flush on front-end socket fails.
The original report is
[pgpool-general: 4265] Pgpool - connection hangs in DISCARD ALL
The patch was generated by Usama and Pawel Ufnalewski<archon at foap.com>,
and Gerhard Wiesinger <lists at wiesinger.com> helped to verify and test
the fix.
- Fix a reset query stuck problem (Tatsuo Ishii)
After receiving X message from frontend, if pgpool-II detects EOF on
the connection before sending reset query, pgpool-II could wait for
a response from backend which had not received the reset query.
To fix this, if EOF received, treat this as FRONTEND_ERROR, rather
than ERROR.
See "[pgpool-hackers: 1440] Yet another reset query stuck problem"
for more details.
- Fix query stuck problems in streaming replication mode with extended
protocol queries (Tatsuo Ishii)
This fix is for both bug #167 and #168.
- Fix pgpool hung after receiving error state from backend (Tatsuo Ishii)
This could happend if we execute an extended protocol query and it
fails.
Per bug #169.
- Fix bug that child processes exit and are not re-spawned (Muhammad Usama)
The problem was due to a logical mistake in the code for checking the
exiting child process type when the watchdog is enabled. Also the severity
of the message emitted for child exits due to max connection reached
from FATAL to LOG.
Per [pgpool-general: 4519] Worker Processes Exit and Are Not Re-spawned
- Fix typo in configure (Tatsuo Ishii)
Patch provided by Thomas Munro.
- doc: Change description of backend_flag (Tatsuo Ishii)
It is pointed out that restarting pgpool-II is not necessary.
Per [pgpool-general-jp: 1394].
- doc: Fix installation procedure. (Tatsuo Ishii)
With PostgreSQL 9.4 or later, installing pgpool_regclass is not needed.
- test: Fix pgpool_setup to not confuse log output (Tatsuo Ishii)
Before it simply redirects stdout and stderr of pgpool processes to
a log file. This could cause the log contents being garbled or even
missed because of race condition caused by multiple process being
writing concurrently.
To fix this, pgpool_setup now generates startall script in which pgpool
sends stdout/stderr to cat command by pipe, and cat writes to the log
file.
- Fix to validate the PCP packet length (Muhammad Usama)
Without the validation check, a malformed PCP packet can crash the
PCP child and/or can run the server out of memory by sending the packet
with a very large data size.
===============================================================================
3.4.5 (tataraboshi) 2016/04/01
* Version 3.4.5
This is a bugfix release against pgpool-II 3.4.4.
__________________________________________________________________
* Bug fixes
- test: Fix test/regression/clean.sh to remove binary files of
010.rewrite_timestamp test (Yugo Nagata)
- Fix memorry leak reported by Coverity (CID 1350095) (Yugo Nagata)
- Fixing pgpool-recovery module compilation issue with PostgreSQL 9.6
(Muhammad Usama)
Incorporating the change of function signature for GetConfigOption..()
functions in PostgreSQL 9.6.
- Fix a reset query stuck problem (Muhammad Usama)
The solution is to report FRONTEND_ERROR instead of simple ERROR when
pool_flush on front-end socket fails.
The original report is
[pgpool-general: 4265] Pgpool - connection hangs in DISCARD ALL
The patch was generated by Usama and Pawel Ufnalewski<archon at foap.com>,
and Gerhard Wiesinger <lists at wiesinger.com> helped to verify and test
the fix.
- Fix typo in configure (Tatsuo Ishii)
Patch provided by Thomas Munro.
- doc: Change description of backend_flag (Tatsuo Ishii)
It is pointed out that restarting pgpool-II is not necessary.
Per [pgpool-general-jp: 1394].
- doc: Fix installation procedure. (Tatsuo Ishii)
With PostgreSQL 9.4 or later, installing pgpool_regclass is not needed.
- test: Fix pgpool_setup to not confuse log output (Tatsuo Ishii)
Before it simply redirects stdout and stderr of pgpool processes to
a log file. This could cause the log contents being garbled or even
missed because of race condition caused by multiple process being
writing concurrently.
To fix this, pgpool_setup now generates startall script in which pgpool
sends stdout/stderr to cat command by pipe, and cat writes to the log
file.
- Fix to validate the PCP packet length (Muhammad Usama)
Without the validation check, a malformed PCP packet can crash the
PCP child and/or can run the server out of memory by sending the packet
with a very large data size.
===============================================================================
3.3.9 (tokakiboshi) 2016/04/01
* Version 3.3.9
This is a bugfix release against pgpool-II 3.3.8.
__________________________________________________________________
* Bug fixes
- test: Fix test/regression/clean.sh to remove binary files of
010.rewrite_timestamp test (Yugo Nagata)
- Fix memorry leak reported by Coverity (CID 1350095) (Yugo Nagata)
- Fixing pgpool-recovery module compilation issue with PostgreSQL 9.6
(Muhammad Usama)
Incorporating the change of function signature for GetConfigOption..()
functions in PostgreSQL 9.6.
- Fix typo in configure (Tatsuo Ishii)
Patch provided by Thomas Munro.
- doc: Change description of backend_flag (Tatsuo Ishii)
It is pointed out that restarting pgpool-II is not necessary.
Per [pgpool-general-jp: 1394].
- doc: Fix installation procedure. (Tatsuo Ishii)
With PostgreSQL 9.4 or later, installing pgpool_regclass is not needed.
- test: Fix pgpool_setup to not confuse log output (Tatsuo Ishii)
Before it simply redirects stdout and stderr of pgpool processes to
a log file. This could cause the log contents being garbled or even
missed because of race condition caused by multiple process being
writing concurrently.
To fix this, pgpool_setup now generates startall script in which pgpool
sends stdout/stderr to cat command by pipe, and cat writes to the log
file.
- Fix to validate the PCP packet length (Muhammad Usama)
Without the validation check, a malformed PCP packet can crash the
PCP child and/or can run the server out of memory by sending the packet
with a very large data size.
- Fix a reset query stuck problem (Muhammad Usama)
The solution is to return POOL_END_WITH_FRONTEND_ERROR instead of
POOL_END when pool_flush on front-end socket fails.
The original report is
[pgpool-general: 4265] Pgpool - connection hangs in DISCARD ALL
===============================================================================
3.2.14 (namameboshi) 2016/04/01
* Version 3.2.14
This is a bugfix release against pgpool-II 3.2.13.
__________________________________________________________________
* Bug fixes
- doc: Change description of backend_flag (Tatsuo Ishii)
It is pointed out that restarting pgpool-II is not necessary.
Per [pgpool-general-jp: 1394].
- doc: Fix installation procedure. (Tatsuo Ishii)
With PostgreSQL 9.4 or later, installing pgpool_regclass is not needed.
- Fix to validate the PCP packet length (Muhammad Usama)
Without the validation check, a malformed PCP packet can crash the
PCP child and/or can run the server out of memory by sending the packet
with a very large data size.
- Fix a reset query stuck problem (Muhammad Usama)
The solution is to return POOL_END_WITH_FRONTEND_ERROR instead of
POOL_END when pool_flush on front-end socket fails.
The original report is
[pgpool-general: 4265] Pgpool - connection hangs in DISCARD ALL
===============================================================================
3.1.17 (hatsuiboshi) 2016/04/01
* Version 3.1.17
This is a bugfix release against pgpool-II 3.1.16.
__________________________________________________________________
* Bug fixes
- doc: Change description of backend_flag (Tatsuo Ishii)
It is pointed out that restarting pgpool-II is not necessary.
Per [pgpool-general-jp: 1394].
- doc: Fix installation procedure. (Tatsuo Ishii)
With PostgreSQL 9.4 or later, installing pgpool_regclass is not needed.
- Fix to validate the PCP packet length (Muhammad Usama)
Without the validation check, a malformed PCP packet can crash the
PCP child and/or can run the server out of memory by sending the packet
with a very large data size.
- Fix a reset query stuck problem (Muhammad Usama)
The solution is to return POOL_END_WITH_FRONTEND_ERROR instead of
POOL_END when pool_flush on front-end socket fails.
The original report is
[pgpool-general: 4265] Pgpool - connection hangs in DISCARD ALL
===============================================================================
--
Yugo Nagata <nagata at sraoss.co.jp>
More information about the pgpool-general
mailing list