[Pgpool-general] pgpool-II 3.0.5 released

[Toshihiro Kitagawa]

On Mon, 31 Oct 2011 19:40:40 +0900
Nozomi Anzai <anzai at sraoss.co.jp> wrote:

> pgpool Global Development Group is pleased to announce the availability
> of pgpool-II 3.0.5, the latest stable version of pgpool-II 3.0 series.
> 
> This version fixes various bugs since 3.0.4.

We forgot to write an important change.

-----------------------------------------------------------------------
* Incompatible change
-----------------------------------------------------------------------

- Change the lock method of insert_lock. The previous insert_lock uses
  row locking against the sequence relation, but the current one uses
  row locking against pgpool_catalog.insert_lock table. The reason is
  that PostgreSQL core developers decided to disallow row locking
  against the sequence relation to avoid an internal error which it
  leads. So creating insert_lock table in all databases which are
  accessed via pgpool-II beforehand is required. If does not exist
  insert_lock table, pgpool-II locks the insert target table. This
  behavior is same as pgpool-II 2.2 and 2.3 series. If you want to use
  insert_lock which is compatible with older releases, you can specify
  lock method by configure options: --enable-sequence-lock,
  --enable-table-lock(Kitagawa)

> -----------------------------------------------------------------------
> * Bug fixes
> -----------------------------------------------------------------------
> 
> - Fix bug with the handling of empty queries. The empty queries
>   come to be handled the same as SELECT queries. This fix allows
>   load-balance after the empty query(Kitagawa)
> 
> - Fix insert_lock so that it works correctly even if the column
>   definition such as "DEFAULT nextval(('"x_seq"'::text)::regclass)"
>   (Kitagawa)
> 
> - Fix log message which is emitted when pgpool-II cannot parse the
>   query in the extended query protocol so that it shows the query
>   (Kitagawa)
> 
> - Fix description about backend_weight inpgpool-II manual. It can
>  be changed by reloading pgpool.conf(Tatsuo)
> 
> - Fix bug which does not update the node status when reattaching the
>   node in raw mode(Guillaume Lelarge)
> 
> - Fix bug that SELECTs which have subquery with FOR SHARE/UPDATE clause
>   are sent to slave/standby(Tatsuo)
> 
> - Fix bug which rewriting timestamp of default value fails in PREPARE
>   statements. This used to work but was broken in 3.0(Kitagawa)
> 
> - Fix crash of pgpool child when frontend connects if in raw mode,
>   enable_hba is off and more than 2 backends(Kitagawa)
> 
> - Fix some memory leaks(Kitagawa)
> 
> -----------------------------------------------------------------------
> * Enhancements
> -----------------------------------------------------------------------
> 
> - Allow time stamp rewriting to work with arbitrary expression in
>   default value of a column. Before we detected anything including
>   rewriting of default value. for example, timezone('utc'::text, now()).
>   Note that, however, this only adopts to simple queries. Extended
>   protocols(for example Java, PHP PDO) or SQL "PREPARE" still remain
>   same(Tatsuo)
> 
> - Change error message "do_md5: read_password_packet failed" into debug
>   level(Kitagawa)
> 
> -----------------------------------------------------------------------
> 
> 
> You can download the source code from:
> http://pgfoundry.org/frs/download.php/3164/pgpool-II-3.0.5.tar.gz
> 
> -- 
> Nozomi Anzai
> SRA OSS, Inc. Japan
> _______________________________________________
> Pgpool-general mailing list
> Pgpool-general at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgpool-general
>