Re: psycopg, pgpool and closing connections
От | Daniele Varrazzo |
---|---|
Тема | Re: psycopg, pgpool and closing connections |
Дата | |
Msg-id | CA+mi_8b+MQxCVYgV3n_kf1pfrkSY+ESYYAYokqj_r_SsEaUw7Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: psycopg, pgpool and closing connections (Marko Kreen <markokr@gmail.com>) |
Список | psycopg |
On Wed, Oct 5, 2011 at 3:19 PM, Marko Kreen <markokr@gmail.com> wrote: > On Wed, Oct 5, 2011 at 3:26 PM, Daniele Varrazzo > <daniele.varrazzo@gmail.com> wrote: >> I'm after a StackOverflow question >> <http://stackoverflow.com/questions/7658714/psycopg2-pgbouncer-async-mode-with-gevent-error/> >> where the user reports pgpool closing connections used by Python. Part >> of them were about the issue we discussed on the ML one year ago, >> where connections closed in transaction are discarded with "unclean >> server". But after he has ensured clear transactions, still pgpool >> drops the connections with "client close request". > > pgbouncer "client close request" is client-only. > It will be in log on pqfinish(). It will not affect server. > > If you dont see "unclean server", the server is still in pool. Thank you Marko, I think the user was only scared by the "client close request" in the logs. I've invited him to write to this ML in case he has still any doubt. -- Daniele
В списке psycopg по дате отправления: