<div dir="ltr"><div>Just perfect!<br><br></div>Thanks a lot for this really fast resolution.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/14 Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">>> Hello all.<br>
>><br>
>> I tried Pgpool-II 3.2.4 and it seems that the pgpool_regclass is now<br>
>> mandatory?<br>
>> Indeed pgpool have degenerated a node just after I put the 3.2.4 version in<br>
>> production; here is the logs:<br>
>><br>
>> May 13 09:55:00 node1 pgpool-II[10714]: connection received: host=192.0.0.7<br>
>> port=36766<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: do_query: error message from<br>
>> backend function "pgpool_regclass(cstring)" does not exist<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: do_query: error message from<br>
>> backend current transaction is aborted, commands ignored until end of<br>
>> transaction block<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: do_query: error message from<br>
>> backend current transaction is aborted, commands ignored until end of<br>
>> transaction block<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: pool_send_and_wait: Error or notice<br>
>> message from backend: : DB node id: 0 backend pid: 10736 statement: INSERT<br>
>> INTO blablabla; message: current transaction is aborted, commands ignored<br>
>> until end of transaction block<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: read_kind_from_backend: 1 th kind C<br>
>> does not match with master or majority connection kind E<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: kind mismatch among backends.<br>
>> Possible last query was: "INSERT INTO blablabla;" kind details are: 0[E:<br>
>> current transaction is aborted, commands ignored until end of transaction<br>
>> block] 1[C]<br>
>> May 13 09:55:00 node1 pgpool-II[10714]: degenerate_backend_set: 1 fail over<br>
>> request from pid 10714<br>
>> May 13 09:55:00 node1 pgpool-II[10169]: starting degeneration. shutdown<br>
>> host 192.0.0.19(5432)<br>
>> May 13 09:55:00 node1 pgpool-II[10169]: Restart all children<br>
>> May 13 09:55:00 node1 pgpool-II[10169]: execute command: sudo<br>
>> /usr/bin/block_failed_db 1 &<br>
>> May 13 09:55:00 node1 pgpool-II[10169]: failover: set new primary node: -1<br>
>> May 13 09:55:00 node1 pgpool-II[10169]: failover: set new master node: 0<br>
>> May 13 09:55:00 node1 pgpool-II[10169]: failover done. shutdown host<br>
>> 192.0.0.19(5432)<br>
>> May 13 09:55:00 node1 pgpool-II[10316]: worker process received restart<br>
>> request<br>
>> May 13 09:55:00 node1 pgpool-II[10756]: connection received:<br>
>> host=192.0.0.117 port=54452<br>
>><br>
>> I never added the table to my databases before (even I know that it's<br>
>> "strongly recommended" in the documentation) and I'm using PgPool since<br>
>> several years now.<br>
>> According to releases notes I guess this is related to the changes about<br>
>> pool_has_pgpool_regclass.<br>
>><br>
>> So my question is: does I really need to add the pgpool_regclass in my<br>
>> databases or it's a side effect of the 3.4.8 which could be corrected in<br>
>> the future?<br>
><br>
> No, it's not intentional that pgpool-II 3.2.4 requires<br>
> pgpool_regclass() (if it is so). Will look into this.<br>
<br>
</div></div>It turned out that it's a bug with 3.2.4. Attached patch should fix<br>
the problem. Please try it.<br>
<div class="HOEnZb"><div class="h5">--<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>
</div></div></blockquote></div><br></div>