| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | 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-12 17:07:04 |
| Message-ID: | 5734B838.5010606@timbira.com.br |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
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.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-05-12 17:09:24 | Re: 9.6 -> 10.0 |
| Previous Message | Alvaro Herrera | 2016-05-12 17:00:36 | Re: New versioning scheme |