Re: [Pgpool-general] pgpool-II 3.0.5 released
Hi, Why one more release of pgpool-II 3.0 series when we have pgpool-II 3.1 series released already? We were using pgpool-II 3.0.3 and then updated to 3.1. Now, you have released 3.0.5. Which one should we use for production? From: Guillaume Lelarge guilla...@lelarge.info To: Stevo Slavić ssla...@gmail.com Cc: pgpool-general@pgfoundry.org Sent: Tuesday, November 8, 2011 1:36 AM Subject: Re: [Pgpool-general] pgpool-II 3.0.5 released On Mon, 2011-11-07 at 09:18 +0100, Stevo Slavić wrote: Congrats on the release! Is any of the resolved bugs known to be present in 3.1 branch too? Need to decide whether to use 3.1 or 3.0.5 for a production system. I'm especially interested in Fix bug which does not update the node status when reattaching the node in raw mode(Guillaume Lelarge) Don't know about the others, but the one you're referring to is fixed on both releases. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpool-II 3.0.5 released
On Fri, 2011-11-11 at 01:27 -0800, Sandeep Thakkar wrote: Hi, Why one more release of pgpool-II 3.0 series when we have pgpool-II 3.1 series released already? We were using pgpool-II 3.0.3 and then updated to 3.1. Now, you have released 3.0.5. Which one should we use for production? For quite the same reason PostgreSQL gets out minor releases for older branch: that way, you don't have to get the latest major release if an older one works for you. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpool-II 3.0.5 released
Thanks. I was just seeing the changelog and found that the following enhancement in 3.1 is not available in 3.0.5 - Enhance online recovery in streaming replication mode. Now restarting pgpool-II children is avoided when recovery finished. So existing sessions can be continued while doing online recovery(Tatsuo) If we decide to use version 3.1, then I see there are new directives added. For example, backend_flag, follow_master_command, pcp_promte_node_command. Infact, I tried using version 3.1 and used backend_flag and but not follow_master_command. and I see that failover does not work fine. Why do we have this directive when we already have failover_command? Please help! From: Guillaume Lelarge guilla...@lelarge.info To: Sandeep Thakkar sandee...@yahoo.com Cc: Stevo Slavić ssla...@gmail.com; pgpool-general@pgfoundry.org pgpool-general@pgfoundry.org Sent: Friday, November 11, 2011 3:08 PM Subject: Re: [Pgpool-general] pgpool-II 3.0.5 released On Fri, 2011-11-11 at 01:27 -0800, Sandeep Thakkar wrote: Hi, Why one more release of pgpool-II 3.0 series when we have pgpool-II 3.1 series released already? We were using pgpool-II 3.0.3 and then updated to 3.1. Now, you have released 3.0.5. Which one should we use for production? For quite the same reason PostgreSQL gets out minor releases for older branch: that way, you don't have to get the latest major release if an older one works for you. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpool-II 3.0.5 released
On Mon, 2011-11-07 at 09:18 +0100, Stevo Slavić wrote: Congrats on the release! Is any of the resolved bugs known to be present in 3.1 branch too? Need to decide whether to use 3.1 or 3.0.5 for a production system. I'm especially interested in Fix bug which does not update the node status when reattaching the node in raw mode(Guillaume Lelarge) Don't know about the others, but the one you're referring to is fixed on both releases. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpool-II 3.0.5 released
On Mon, 31 Oct 2011 19:40:40 +0900
Nozomi Anzai an...@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@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
