> We have been working for pgpool-II 3.1 for a while. Here are some > TODOs for 3.1.
Revisiting this again. > 1) Re-implement insert_lock. Next PostgreSQL version will not allow us > to use the current implementation of insert_lock. Toshihiro is > working on this problem (this will be backported to 3.0.x). Done. > 2) Allow to specify "DISALLOW_TO_FAILOVER" flag. Patches have been just > proposed. Will commit soon unless there's an objection. Done. > 3) pgpool_adm functions. Just committed. Need to add docs. Also need to > add more functions? Jehan-Guillaume, has it finished? > 4) French docs. Jean-Paul is working on this. Jean-Paul, current status? > 5) German docs. Marcus Wanner is working on this. Marcus Wanner, current status? > 6) Update pgpoolAdmin as usual. Nozomi will work on this. 7) Refactoring pcp_proc_info Patch submitted by Jehan-Guillaume and reviewed by me. Jehan-Guillaume, is it ready for commit? 8) Subject: [Pgpool-general] pgpool-II-3.0.3and4 memory leaks From: takehiro wada <[email protected]> Anyone working on this? > Am I missing something? > > I personaly hope we will finish all of items by July 14th because I'm > going to give a talk in China on the date:-) > > Comments? > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > _______________________________________________ > Pgpool-hackers mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgpool-hackers _______________________________________________ Pgpool-hackers mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-hackers
