<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 7, 2014 at 4:54 AM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">> Tatsuo,<br>
> What is the remaining todo list for 3.4? Do you have a beta date in mind?<br>
<br>
</div>Out of our TODOs: (<a href="http://pgpool.net/mediawiki/index.php/TODO" target="_blank">http://pgpool.net/mediawiki/index.php/TODO</a>)<br>
1.1 Enhance performance of extended protocol case<br>
1.2 Ability to load balance based on Client IP, database, table etc.<br>
1.3 Automatically reattach a node in streaming master/slave configuration<br>
1.4 Allow to use client encoding<br>
1.5 Send read query only to standbys even after fail over<br>
1.6 Recognize multi statemnet queries<br>
1.7 Cursor statements are not load balanced, sent to all DB nodes in replication mode<br>
1.8 Support IPV6 network<br>
1.9 Handle abnormal down of virtual IP interface when watchdog enabled<br>
1.10 Do not invalidate query cache created in a transaction in some cases<br>
1.11 Fix memory leak in pool_config.c<br>
1.12 Add SET commnad<br>
1.13 Put together a definition of error codes into a single header file<br>
1.14 Create separate process for health checking<br>
1.15 Import PostgreSQL's latch module<br>
1.16 Remove parallel query<br>
1.17 Add switch to control select(2) time out in connecting to PostgreSQL<br>
<br>
I think followings are important and could be doable for 3.4:<br>
<br>
1.2 Ability to load balance based on Client IP, database, table etc.<br>
1.11 Fix memory leak in pool_config.c<br>
1.17 Add switch to control select(2) time out in connecting to PostgreSQL<br>
<br>
Also remember that we should fix all issues reported by Coverity.<br>
<br>
Probably this is also very important:<br>
1.1 Enhance performance of extended protocol case<br></blockquote><div><br></div><div>Some of the above items like fixing all coverity issues and 1.1 might be very time consuming. This could impact the release date for 3.4.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
but I don't know how to implement at this moment.<br>
<div class="HOEnZb"><div class="h5"><br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
<br>
>> > Hi<br>
>> ><br>
>> > Please find the attached mega patch for importing the PG94 parser.<br>
>> ><br>
>> > --Usama<br>
>> ><br>
>> ><br>
>> > On Fri, Jun 27, 2014 at 6:26 AM, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>><br>
> wrote:<br>
>> ><br>
>> >> Usama,<br>
>> >><br>
>> >> I have briefly looked into your patches and it seems they are good.<br>
>> >> Also I have tested a few 9.4's new syntax and pgpool-II successfully<br>
>> >> handles it. Good work! Please go head.<br>
>> >><br>
>> >> Best regards,<br>
>> >> --<br>
>> >> Tatsuo Ishii<br>
>> >> SRA OSS, Inc. Japan<br>
>> >> English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
>> >> Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
>> >><br>
>> >> > Usama,<br>
>> >> ><br>
>> >> > Thank you very much for the work.<br>
>> >> > I will look into this.<br>
>> >> ><br>
>> >> > Best regards,<br>
>> >> > --<br>
>> >> > Tatsuo Ishii<br>
>> >> > SRA OSS, Inc. Japan<br>
>> >> > English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
>> >> > Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
>> >> ><br>
>> >> >> Hi<br>
>> >> >><br>
>> >> >> I am working on updating pgpool-II parser to PG94's parser, and till<br>
>> >> time I<br>
>> >> >> have imported the changes from PostgreSQL source to pgpool-II,<br>
> There are<br>
>> >> >> still some TODOs and compiler warnings needed to be fixed, which I<br>
> am<br>
>> >> >> currently working on and hopefully be finished soon. Meanwhile can<br>
> you<br>
>> >> >> please review the attached WIP patch if I have missed or overdone<br>
>> >> something.<br>
>> >> >><br>
>> >> >> Thanks<br>
>> >> >> Usama<br>
>> >> > _______________________________________________<br>
>> >> > pgpool-hackers mailing list<br>
>> >> > <a href="mailto:pgpool-hackers@pgpool.net">pgpool-hackers@pgpool.net</a><br>
>> >> > <a href="http://www.pgpool.net/mailman/listinfo/pgpool-hackers" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-hackers</a><br>
>> >><br>
>> _______________________________________________<br>
>> pgpool-hackers mailing list<br>
>> <a href="mailto:pgpool-hackers@pgpool.net">pgpool-hackers@pgpool.net</a><br>
>> <a href="http://www.pgpool.net/mailman/listinfo/pgpool-hackers" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-hackers</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Ahsan Hadi<br>Snr Director Product Development<br>EnterpriseDB Corporation<br>The Enterprise Postgres Company<br><br>Phone: +92-51-8358874 <br>Mobile: +92-333-5162114<br>
<br>Website: <a href="http://www.enterprisedb.com">www.enterprisedb.com</a><br>EnterpriseDB Blog: <a href="http://blogs.enterprisedb.com/">http://blogs.enterprisedb.com/</a><br>Follow us on Twitter: <a href="http://www.twitter.com/enterprisedb">http://www.twitter.com/enterprisedb</a><br>
<br>This e-mail message (and any attachment) is intended for the use of the individual or entity to whom it is addressed. This message contains information from EnterpriseDB Corporation that may be privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient or authorized to receive this for the intended recipient, any use, dissemination, distribution, retention, archiving, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete this message.
</div></div>