<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 28, 2017 at 11:20 AM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@sraoss.co.jp" target="_blank">ishii@sraoss.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> On Fri, Apr 28, 2017 at 5:47 AM, Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp">ishii@sraoss.co.jp</a>> wrote:<br>
><br>
>> Usama,<br>
>><br>
>> Unfortunately after applying your patches, pgpool won't start any<br>
>> more. Here's back trace info. pgpool.conf attached.<br>
>><br>
><br>
</span>> I think you need to delete *src/config/pool_config.c* and<br>
> *src/tools/pgmd5/pool_config.<wbr>c* autogenerated files before building the<br>
<span class="">> Pgpool-II, The reason being the memory for POOL_CONFIG->health_check_<wbr>params<br>
> is allocated in pgpool_config.l and apparently the make is not regenerating<br>
> the pgpool_config.c.<br>
<br>
</span>Oh, I totaly forget about it. Will try again...<br>
<span class=""><br>
> I was also wondering that we could use the array for health_check_params in<br>
> POOL_CONFIG rather than a pointer and allocating it dynamically.<br>
<br>
</span>But it requires health_check_params * MAX_NUM_BACKENDS (=128 for now)<br>
memory. Sounds like waste of meory...<br></blockquote><div><br></div><div>Yes true, But we are already allocating the same amount of memory dynamically. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_<wbr>en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.<wbr>jp</a><br>
</div></div></blockquote></div><br></div></div>