[pgpool-hackers: 158] Re: [Pgpool-hackers] Reload does not help if password file changed

[Gurjeet Singh]

On Thu, Nov 8, 2012 at 6:56 PM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> >> > I understand that this patch was committed on 2011-09-29, and pgpool
> 3.1
> >> > was released on 2011-09-08. So quite possibly the answer to the next
> >> > question is no.
> >> >
> >> > Can you please confirm if pgpool 3.1 has this fix?
> >>
> >> No. However it recently comes in 3.1 stable tree. See [pgpool-general:
> >> 1146] and upthread for more details.
> >>
> >
> > Are you talking about this  thread?
>
> No. This one.
>
> http://www.pgpool.net/pipermail/pgpool-general/2012-October/001165.html
>
> > http://www.pgpool.net/pipermail/pgpool-general/2012-October/001146.html
> >
> > I couldn't see anything relevant to pool_passwd.conf reload in that
> thread!
> >
> > Can you please explain what you meant by 'it recently comes to 3.1'. Does
> > it mean that this feature will be available in next minor version of
> 3.1.x?
>
> Yes.
>

I am glad to see commit  d5930588747f1d0759411f494714a7909efe5e35 land in
version 3.1; it wasn't committed to stable branches despite my argument at
the time that it is a bug, and not a new feature.

<snip>
Also, would it be possible to back-patch this to previous stable versions?
As my earlier complaints, I wouldn't treat this as new feature, but a bug
which always got overlooked, because SIGHUP is always supposed to reload
the config files and yet password changes were never updated. My 2 cents.
</snip>

-- 
Gurjeet Singh

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