I recieve the following error very *occasionally* from a couple of
different django apps running against Postgres (some backtrace
included for context):

 File "/opt/django/trunk/django/db/models/query.py", line 188, in
iterator
   cursor = connection.cursor()

 File "/opt/django/trunk/django/db/backends/__init__.py", line 33, in
cursor
   cursor = self._cursor(settings)

 File "/opt/django/trunk/django/db/backends/postgresql/base.py", line
98, in _cursor
   self.connection = Database.connect(conn_string, **self.options)

OperationalError: could not connect to server: No such file or
directory
       Is the server running locally and accepting
       connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.
5432"?

It's not consistent, and I have not been able to successfully
replicate it.  It seems to happen when the sites are receiving
traffic.  I know it's a Postgres error, but I thought since a lot of
Django users deploy against postgres someone might know something
about this.  This latest error came from an app running psycopg
against 8.1.11.  I'm 95% confident I've seen the same error on an app
running psycopg2 against 8.2.5.

Is it really just a matter of tweaking the postgresql.conf
(max_connections et al)?

Thanks!
doug.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to