[pgpool-hackers: 128] Re: Enabling -D switch of pgpool by default

[Gurjeet Singh]

On Wed, Sep 12, 2012 at 5:45 PM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> > So far I haven't heard of any damaging or detrimental effects of -D
> option.
> > The only effect and overhead that I can verify is that with -D option
> > pgpool will connect to every backend_hostname to verify whether the
> > database backend is reachable. This may cause some slowdown in initial
> > pgpool startup, but the upside is that the backend_status value reflects
> > the true status of a backend.
>
> Really? At least Alex and I are not sure if it's a really good idea,
> while no one is with your idea. Also I would like to hear from Devrim
> since he is the mainter of init scripts.
>

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.

Best regards,
-- 
Gurjeet Singh

http://gurjeet.singh.im/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20120912/71b0a78e/attachment.html>