psycopg, pgpool and closing connections - Mailing list psycopg

From Daniele Varrazzo
Subject psycopg, pgpool and closing connections
Date
Msg-id CA+mi_8bjUJuj8gC3BaCctACF-JrR7XP6911tfUT=Cy8s2hf=tQ@mail.gmail.com
Whole thread Raw
Responses Re: psycopg, pgpool and closing connections  (Marko Kreen <markokr@gmail.com>)
List 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

psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: so, is connection.poll() supposed to block?
Next
From: Marko Kreen
Date:
Subject: Re: psycopg, pgpool and closing connections