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
