| From: | Christian Jauvin <cjauvin(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: PgBouncer doubts |
| Date: | 2014-06-11 14:26:36 |
| Message-ID: | CAJSE4To-i7rXLan6fHM-sr9M-iC7serDJ2+1-Z1_YAcbRfsGfQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
> To make things clearer, what log are we looking at, the PgBouncer or
> Postgres?
This is the PgBouncer log.
> The log is showing that the client is requesting that the connection be
> closed. So my guess is that teardown_request is being run for a reason you
> have not accounted for.
Actually, teardown_request should be executed for every single
interaction with the app (after every Ajax call for instance), so one
thing I tried (under the assumption that maybe the psycopg2 connection
should not be explicitly closed in such a PgBouncer-enabled setup) is
to simply comment it all out, but it didn't change the PgBouncer
behavior at all.
Also, according to this answer to the same question on dba.SE, it
seems that this log is
the expected behavior:
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-06-11 15:28:40 | Re: PgBouncer doubts |
| Previous Message | Adrian Klaver | 2014-06-11 14:14:39 | Re: PgBouncer doubts |