Re: The uselessness of pgbouncer PAUSE

On Thu, Jan 16, 2014 at 2:22 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>> It would be nice to use PAUSE for reloading the configuration after, for
>>> example, adding a new replica to the pool. However, that would take a
>>> lot of experimentation to see if it even works.
>>
>> You just need to RELOAD if you added/changed something in the
>> [database] section of config. It will handle everything itself AFAIK.
>
> The real issue here is that PAUSE can hang indefinitely. What happens
> if I do RELOAD without doing PAUSE?

I meant just RELOAD without PAUSE in case of adding a new replica. It
will simply start working with new entries you added to the [database]
section and change the way it worked with the existing ones that were
changed.

ps. Returning to the PAUSE - it can be prevented from hanging
indefinitely, but, yes, as you noted, it might require a lot of
additional logic and experimenting.

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com