| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Devrim Gunduz <devrim(at)gunduz(dot)org>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: 9.6 -> 10.0 |
| Date: | 2016-05-13 20:41:23 |
| Message-ID: | 20160513204123.GA10332@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Thu, May 12, 2016 at 02:07:04PM -0300, Euler Taveira wrote:
> On 12-05-2016 13:09, Bruce Momjian wrote:
> > That is an interesting approach. How many applications are prepared to
> > re-sent a transaction block based on the error returned by pgbouncer in
> > this case?
> >
> FYI, pgBouncer does not error out transactions. While in PAUSE mode,
> pgBouncer waits for the current transactions to finish and the new ones
> are put in a wait queue. After the RESUME command, pgBouncer sends the
> transaction in the wait queue. Of course, if your application has a
> response timeout you will see cancellations.
Oh, that seems useful.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh berkus | 2016-05-13 20:45:04 | Re: 9.6 -> 10.0 |
| Previous Message | Robert Haas | 2016-05-13 20:19:03 | Re: When should be advocate external projects? |