[pgpool-hackers: 2302] Re: RFC: New health check implementation

Muhammad Usama m.usama at gmail.com
Fri Apr 28 15:24:10 JST 2017


On Fri, Apr 28, 2017 at 11:20 AM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> > On Fri, Apr 28, 2017 at 5:47 AM, Tatsuo Ishii <ishii at sraoss.co.jp>
> wrote:
> >
> >> Usama,
> >>
> >> Unfortunately after applying your patches, pgpool won't start any
> >> more. Here's back trace info. pgpool.conf attached.
> >>
> >
> > I think you need to delete  *src/config/pool_config.c* and
> > *src/tools/pgmd5/pool_config.c* autogenerated files before building the
> > Pgpool-II, The reason being the memory for POOL_CONFIG->health_check_
> params
> > is allocated in pgpool_config.l and apparently the make is not
> regenerating
> > the pgpool_config.c.
>
> Oh, I totaly forget about it. Will try again...
>
> > I was also wondering that we could use the array for health_check_params
> in
> > POOL_CONFIG rather than a pointer and allocating it dynamically.
>
> But it requires health_check_params * MAX_NUM_BACKENDS (=128 for now)
> memory. Sounds like waste of meory...
>

Yes true, But we are already allocating the same amount of memory
dynamically.


> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20170428/a9d164f3/attachment.html>


More information about the pgpool-hackers mailing list