Re: The uselessness of pgbouncer PAUSE

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
Cc: SF Postgres <sfpug(at)postgresql(dot)org>
Subject: Re: The uselessness of pgbouncer PAUSE
Date: 2014-01-16 22:22:46
Message-ID: 52D85BB6.3030302@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: sfpug


>> 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?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse sfpug by date

  From Date Subject
Next Message Sergey Konoplev 2014-01-16 22:33:30 Re: The uselessness of pgbouncer PAUSE
Previous Message Sergey Konoplev 2014-01-16 22:22:21 Re: The uselessness of pgbouncer PAUSE