Comment #1 on issue 15 by carl.j.meyer: Postgres 8.3.3 and
send_all: "unexpected EOF on client connection"
http://code.google.com/p/django-mailer/issues/detail?id=15
Ok, this seems to be a more general problem; Postgres gives this error if
the
connection isn't closed properly, so any Django management command (or even
just
playing around in ./manage.py shell) will trigger it if it doesn't
explicitly call
django.db.connection.close() before exiting. (Django explicitly closes its
connection at the end of a normal request/response cycle). Normally not a
big deal,
but since send_mail is typically called so frequently, maybe it would be
worth adding
an explicit connection.close to help out Postgres users? I'm certainly
patching my
copy to do that; patch attached if anyone else wants it.
Attachments:
issue15.diff 564 bytes
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pinax-updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pinax-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
