[pgpool-general: 3389] Re: [PATCH] pgpool2 parent process doesn't finish if init_system_db_connection fails
m.usama at gmail.com
Mon Dec 29 23:00:53 JST 2014
Thanks for pointing out the problem and for the patch. This issue is not
only confined to the errors coming from init_system_db_connection(). The
problem is that the overall behavior of pgpool is little confused in the
situations of child process start-up failures. So after discussion with
Tatsuo Ishii it was decided that in such cases, the best bid would be to
shutdown pgpool main process and user must fix the problem before
restarting the pgpool-II.
So for fixing this I have patched the ereport() API and reaper() function
to fix the behaviour of system in case of any pgpool-II process has trouble
On Thu, Dec 11, 2014 at 6:43 AM, Sadayuki Furuhashi <frsyuki at gmail.com>
> Sorry, I guess I failed to attach the patch.
> Sadayuki Furuhashi
> http://fluentd.org http://msgpack.org
> 2014/12/10 17:18, Sadayuki Furuhashi <frsyuki at gmail.com>:
> > Hi,
> > I found that init_system_db_connection() calls ereport(ERROR) before
> > An influence of this issue is that child processes won't exit by
> themselves when init_system_db_connection()
> > fails and sending SIGTERM to the parent process doesn't complete
> shutdown process appropriately.
> > This patch replaces ereport(ERROR) with ereport(WARNING) + child_exit(1).
> > A trade-off is that pgpool2 shows a lot of "failed to make persistent
> system db connection" message to the log
> > because a child process exists immediately and the parent process keeps
> restarting them immediately.
> > --
> > Sadayuki Furuhashi
> > http://fluentd.org http://msgpack.org
> > twitter:@frsyuki
> > <system_db_connect_error.patch>
> pgpool-general mailing list
> pgpool-general at pgpool.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pgpool-general