On Fri, May 13, 2011 at 5:12 PM, Otto Vazquez <otto.vazquez@gmail.com> wrote:
> OperationalError: no connection to the server
> We believe it's a connector problem, just google a little and you will find
> lots a posts with same/similar problem.
> Some other useful info/samples:
>
http://stackoverflow.com/questions/1303654/threaded-django-task-doesnt-automatically-handle-transactions-or-db-connections
> http://groups.google.com/group/django-developers/browse_frm/thread/5249b9ba993431ca/4d1b9d65329c8b75
> http://code.djangoproject.com/ticket/9964
Actually it doesn't seem the same issue to me. IIRC with the django
issue you get long running transactions. A possible consequence may be
getting errors like "current transaction is aborted...". But "no
connection to the server" is an error message I have never seen. I
wouldn't even know how to reproduce it just using psycopg: if you
issue a rollback() on a closed connection you don't get that error,
but rather a clean "InterfaceError: connection already closed".
Do you have any middleware software (pgpool etc.) handling the
connection used by psycopg? Anything interfering with the socket?
-- Daniele
