psycopg, pgpool and closing connections

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: psycopg(at)postgresql(dot)org
Subject: psycopg, pgpool and closing connections
Date: 2011-10-05 13:26:54
Message-ID: CA+mi_8bjUJuj8gC3BaCctACF-JrR7XP6911tfUT=Cy8s2hf=tQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

Hello Marko,

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".

psycopg calls PQfinish on the connections when they are destroyed by
python: I am assuming that pgpool intercepts any signal sent to the
server on this event and instead resets a connection and puts it back
to the pool. Am I wrong? Is there anything the user can do, e.g. in
pgpool configuration, to reuse the connections, or the interaction
between pgpool and psycopg is more fundamentally broken?

Thank you.

-- Daniele

Responses

Browse psycopg by date

  From Date Subject
Next Message Marko Kreen 2011-10-05 14:19:58 Re: psycopg, pgpool and closing connections
Previous Message Daniele Varrazzo 2011-10-04 17:11:07 Re: so, is connection.poll() supposed to block?