<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 21, 2016 at 6:11 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-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span>> Hi Ishii-San<br>
><br>
> Can you please have a look at the attached patch, It try to solve this<br>
> "Kind does not match .." problem by ignoring the notice messages while<br>
> reading the backend response in read_kind_from_backend() function<br>
<br>
</span>Doesn't this patch simply ignore important messages like this?<br></blockquote><div><br></div><div>Basically patch only ignores the notice log messages and these messages are important, especially ones with severity level of WARNING and NOTICE, to inform the user about some critical issue. </div><div>I may be wrong, but I don't think these log message are important in terms of PG protocol flow. i.e. notice (kind = 'N') message only contains the log and is delivered to frontend (pgpool-II in our case) depending on <i>client_min_messages</i> settings in postgresql.conf.</div><div>So I think it should be safe to ignore these. </div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div><div><br>
>>> ... WARNING: database "testdb" must be vacuum within 11000000 transaction<br>
<br>
><br>
><br>
> On Tue, Apr 19, 2016 at 1:50 PM, Ahsan Hadi <<a href="mailto:ahsan.hadi@enterprisedb.com" target="_blank">ahsan.hadi@enterprisedb.com</a>><br>
> wrote:<br>
><br>
>> I agree this cause lot of annoyance to pgpool users and something we<br>
>> should address for 3.6.<br>
>><br>
>> Usama,<br>
>> Is this added to 3.6 wiki?<br>
>><br>
>> On Fri, Apr 15, 2016 at 11:46 AM, Muhammad Usama <<a href="mailto:m.usama@gmail.com" target="_blank">m.usama@gmail.com</a>><br>
>> wrote:<br>
>><br>
>>> Hi<br>
>>><br>
>>> pgpool throws ".. kind does not match.." error message when all the<br>
>>> attached backend nodes do not return the same response to the query. Although<br>
>>> this error message can be a symptom of the backend node sync issue in<br>
>>> most cases, but in case when the message kind of backend nodes differs<br>
>>> because one of the backend returned the notice response while the other<br>
>>> returned some other kind then that case should not be considered as an<br>
>>> error case.<br>
>>><br>
>>> Consider the scenario where a pgpool is connected to three backend nodes<br>
>>> and pgpool is expecting to receive "[C] command complete" message from<br>
>>> all nodes for the last query. But while processing the query one of the<br>
>>> backend also produced a warning message.<br>
>>><br>
>>> ... WARNING: database "testdb" must be vacuum within 11000000 transaction<br>
>>><br>
>>> Please note that the query was successful on all attached backend, but<br>
>>> one backend also produced an extra warning message along with the command<br>
>>> complete message.<br>
>>><br>
>>> Now pgpool will throw an error something like<br>
>>><br>
>>> ERROR: pid 720: read_kind_from_backend: 1 th kind N does not match<br>
>>> with master or majority connection kind C<br>
>>><br>
>>> But since the node would also have sent the expected command complete<br>
>>> message after that warning notice, So Ideally, pgpool should ignore the<br>
>>> WARNING message and compare the subsequent message, and only throw an error<br>
>>> if the message from nodes after ignoring notification messages differs.<br>
>>><br>
>>> What are your thoughts on this?<br>
>>><br>
>>> Kind regards<br>
>>> Muhammad Usama<br>
>>><br>
>>><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" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-hackers</a><br>
>>><br>
>>><br>
>><br>
>><br>
>> --<br>
>> 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" rel="noreferrer" target="_blank">www.enterprisedb.com</a><br>
>> EnterpriseDB Blog: <a href="http://blogs.enterprisedb.com/" rel="noreferrer" target="_blank">http://blogs.enterprisedb.com/</a><br>
>> Follow us on Twitter: <a href="http://www.twitter.com/enterprisedb" rel="noreferrer" target="_blank">http://www.twitter.com/enterprisedb</a><br>
>><br>
>> This e-mail message (and any attachment) is intended for the use of the<br>
>> individual or entity to whom it is addressed. This message contains<br>
>> information from EnterpriseDB Corporation that may be privileged,<br>
>> confidential, or exempt from disclosure under applicable law. If you are<br>
>> not the intended recipient or authorized to receive this for the intended<br>
>> recipient, any use, dissemination, distribution, retention, archiving, or<br>
>> copying of this communication is strictly prohibited. If you have received<br>
>> this e-mail in error, please notify the sender immediately by reply e-mail<br>
>> and delete this message.<br>
>><br>
</div></div></blockquote></div><br></div></div>