| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | SF Postgres <sfpug(at)postgresql(dot)org> |
| Subject: | Re: The uselessness of pgbouncer PAUSE |
| Date: | 2014-01-16 22:19:55 |
| Message-ID: | CAL_0b1t6CkBKbqq6o5hsJoBKhc8_T6tCyhJTUCJcQrPGQGS_jA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
On Thu, Jan 16, 2014 at 1:55 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 01/16/2014 01:29 PM, Sergey Konoplev wrote:
> That's far more complicated than just restarting pgbouncer, and doesn't
> solve the problem I was trying to solve. Maybe I'll add something
> later, but right now it's too limited to do anything with.
Sure.
> 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.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Konoplev | 2014-01-16 22:22:21 | Re: The uselessness of pgbouncer PAUSE |
| Previous Message | Josh Berkus | 2014-01-16 22:02:01 | Re: The uselessness of pgbouncer PAUSE |