<div dir="ltr">I agree this cause lot of annoyance to pgpool users and something we should address for 3.6.<div><br></div><div>Usama,</div><div>Is this added to 3.6 wiki?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 15, 2016 at 11:46 AM, Muhammad Usama <span dir="ltr"><<a href="mailto:m.usama@gmail.com" target="_blank">m.usama@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi</div><div><br></div>pgpool throws <span style="font-size:12.8px">".. kind does not match.." error message</span> when all the attached backend nodes<span style="font-size:12.8px"> do not return the same response to the query. </span><span style="font-size:12.8px">Although this </span><span style="font-size:12.8px">error message can be a symptom of the backend node sync issue in most cases, but in case when the message kind of backend nodes differs because one of the backend returned the notice response while the other returned some other kind then that case should not be considered as an error case.</span><div><span style="font-size:12.8px"><br></span><div><span style="font-size:12.8px">Consider the scenario where a pgpool is connected to three backend nodes and pgpool is expecting to receive </span><span style="font-size:12.8px">"[C] command complete" message from all nodes for the last query. But while processing the query one of the backend also produced a warning message.</span></div><div><span style="font-size:12.8px"><br></span></div><div><font face="monospace, monospace"><span style="font-size:12.8px">... WARNING: database "testdb" must be vacuum within 11000000 transaction</span><span style="font-size:12.8px"><br></span></font></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Please note that the query was successful on all attached backend, but one backend also produced an extra warning message along with the command complete message.</span></div><div><br></div><div>Now pgpool will throw an error something like</div><div><span style="font-size:12.8px"><br></span></div><div><font face="monospace, monospace"><span style="font-size:12.8px">ERROR: pid 720: read_kind_from_backend: 1 th kind N does not match with master or majority connection kind C</span><br></font></div><div><span style="font-size:12.8px"><br></span></div><div><div style="font-size:12.8px">But since the node would also have sent the expected command complete message after that warning notice, So Ideally, pgpool should ignore the WARNING message and compare the subsequent message, and only throw an error if the message from nodes after ignoring notification messages differs.</div></div><div><br></div><div><span style="font-size:12.8px">What are your thoughts on this?</span></div></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Kind regards</span></div><span class="HOEnZb"><font color="#888888"><div><span style="font-size:12.8px">Muhammad Usama</span></div><div><span style="font-size:12.8px"><br></span></div></font></span></div>
<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" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-hackers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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" 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>