<div dir="ltr"><div class="gmail_quote">On Wed, Sep 12, 2012 at 5:45 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> So far I haven't heard of any damaging or detrimental effects of -D option.<br>
> The only effect and overhead that I can verify is that with -D option<br>
> pgpool will connect to every backend_hostname to verify whether the<br>
> database backend is reachable. This may cause some slowdown in initial<br>
> pgpool startup, but the upside is that the backend_status value reflects<br>
> the true status of a backend.<br>
<br>
</div>Really? At least Alex and I are not sure if it's a really good idea,<br>
while no one is with your idea. Also I would like to hear from Devrim<br>
since he is the mainter of init scripts.<br></blockquote><div><br>Well, the only argument I have heard is that once added to init script, it will be difficult to disable its effect, like one could do by using $OPTS env variable. What I consider 'damaging or detrimental' is if someone said "That'll cause wrong results in certain mode of operation (say replication)" or "this will cause a crash" or "this will make some backend nodes unavailable via pgpool". If -D option does not cause any unintended effects, I think it is safe for me to use. I hope you get my point.<br>
<br></div></div>Best regards,<br>-- <br><div dir="ltr">Gurjeet Singh<br><br><a href="http://gurjeet.singh.im/" target="_blank">http://gurjeet.singh.im/</a><br></div><br>
</div>