<div dir="ltr">Thanks Tatsuo for your feedback. Please see my response in-line..<div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 12, 2014 at 10:22 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Ahasan,<br>
<br>
I have reviewed you proposal of 9.5 road map (#8, #9 #10 are my<br></blockquote><div><br></div><div>Do you mean 3.5 road map?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
additions). It seems #4, #8, #10 are feasible. I think others need to<br>
be studied or elaborated more.<br></blockquote><div><br></div><div>Are you proposing 4,8,10 for pgpool 3.5? I don't think this would be enough from a feature perspective for a major pgpool release, we need to include a feature or two form the performance or HA type of features. </div><div><br></div><div>You are right we need RND on some of the important items however i feel that we should start that RND work in the current team if no one else picks it up.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
1) performance issue with prepared protocol.<br>
- testing pgpool for query latency and find out where we can make improvement.<br>
<br>
This is already on the TODO list for years now but nobody comes up<br>
with an idea to implement it. I think we will wait for someone<br>
thinks of nice idea.<br></blockquote><div><br></div><div>Yeah this is very important, we should really get someone to look at this for 3.5. The testing of query latency will also give ideas for other performance improvements.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
2) Next steps for HA...Is there a way to provide automatic and<br>
seamless failover for active sessions.<br>
<br>
I have no idea how to implement it. Suppose failover happens while<br>
client is receiving SELECT result data from pgpool-II. We need to<br>
find a way to remember what data has been already sent and not to<br>
switch to different backend and to continue the session.<br>
<br></blockquote><div><br></div><div>I believe Usama is planning to do some RND on watchdog soon. He will <span style="color:rgb(0,0,0);font-family:arial,sans,sans-serif;font-size:13px;white-space:pre-wrap">study the techniques and architecture used by cloud and other systems for HA and propose some enhancements that we can implement for watchdog in pgpool II. </span></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
3) multi master communication. two independent pairs of pgpool needed<br>
to communicate.<br>
<br>
Can you please elaborate what needed for pgpool-II? Sounds vague to me.<br></blockquote><div><br></div><div>Yeah i agree the requirements is a bit vague. Basically we had a customer who was running two pairs of pgpool in two different countries. He wanted to have some sort of multi master communication between the pairs so if a node goes down in one pair, a message is sent to other pair. The clients connecting to one pair </div><div><br></div><div>Usama, Can you give some further clarifications on this since you also looked into the customer query... </div><div><br></div><div>Here is the snippet form the user's email :</div><div><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">As you know, we have a pair of PG-Pool boxes in both of our 2 sites.</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">Each pair </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">uses watchdog to communicate and to manage the VIP. Each pair is </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">configured to</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">use all 4 of the back-end DBs 2 in each site. I have set LB weighting </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">so that</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">the queries are sent to the local DBs in the vast majority of cases.</span></div><div><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">What I think we need to do is make the 2 pairs of PG-Pool communicate </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">so that</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">if a node is detached at one side, this info is passed through to the </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">other</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">PG-Pool pair. I have tried to setup watchdog between all 4 of the </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">PG-Pool boxes</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">and although I can see that the additional WD packets are being sent</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">they don¹t </span><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">seem to be processed at the far end.</span><br style="font-family:arial,sans-serif;font-size:12.7272720336914px"><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
4) parser integration with latest pg version<br>
<br>
Yes, we should integrate PostgreSQL 9.5's parser for pgpool-II 3.5.<br>
<br>
<br>
5) Ability to re-issue queries when it failover to the stand-by node.<br>
Currently the user has re-issue queries<br>
<br>
Looks identical to #2.<br></blockquote><div><br></div><div>Hmm...I believe 2 is about doing a seamless failover for active sessions...</div><div><br></div><div>This one came from Bruce...</div><div><br></div><div>Bruce, do you think 5 and 2 are identical?</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
6) Would like to see pgpool in separate sub modules that can be<br>
installed separately for each feature, along with a common-libs<br>
sub-package or so.<br>
<br>
I have no idea what this actually means. We will wait until someone<br>
comes up with more concrete idea.<br>
<br>
7) Adding transaction based pooling to pgpool<br>
<br>
Probably we should try pgbouncer + pgpool-II combo first to see if<br>
it's actually useful.<br>
<br>
8) Enhance pcp commands<br>
<br>
<a href="http://pgpool.net/mediawiki/index.php/TODO#Enhance_pcp_commands" target="_blank">http://pgpool.net/mediawiki/index.php/TODO#Enhance_pcp_commands</a><br>
<br>
9) create separate process for health checking<br>
<br>
<a href="http://pgpool.net/mediawiki/index.php/TODO#Create_separate_process_for_health_checking" target="_blank">http://pgpool.net/mediawiki/index.php/TODO#Create_separate_process_for_health_checking</a><br>
<br>
10) Create yum repository<br>
<br>
Best regards,<br>
--<br>
Tarts 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>
pgpool-hackers mailing list<br>
<a href="mailto:pgpool-hackers@pgpool.net" target="_blank">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>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Ahsan Hadi<br>Snr Director Product Development<br>EnterpriseDB Corporation<br>The Enterprise Postgres Company<br><br>Phone: <a href="tel:%2B92-51-8358874" value="+92518358874" target="_blank">+92-51-8358874</a> <br>Mobile: <a href="tel:%2B92-333-5162114" value="+923335162114" target="_blank">+92-333-5162114</a><br><br>Website: <a href="http://www.enterprisedb.com" target="_blank">www.enterprisedb.com</a><br>EnterpriseDB Blog: <a href="http://blogs.enterprisedb.com/" target="_blank">http://blogs.enterprisedb.com/</a><br>Follow us on Twitter: <a href="http://www.twitter.com/enterprisedb" target="_blank">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></div>