Modify ↓
#8539 closed defect (fixed)
Problem with pyPgSql
| Reported by: | Owned by: | Remy Blank | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | database backend | Version: | none |
| Severity: | normal | Keywords: | pypgsql |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
Hello! Unfortunately, I can not upload my website at http://browsershots.org/ due. Something is blocking my website, so they couldn't find any connection to the server. There are some particular reasons. But unfortunately I don't understand the problems, so "http://browsershots.org/" recommended your website so that you can solve the problem.
Here is the traceback:
Python Traceback
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 406, in dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 191, in dispatch
chosen_handler = self._pre_process_request(req, chosen_handler)
File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 263, in _pre_process_request
chosen_handler = f.pre_process_request(req, chosen_handler)
File "/usr/lib/python2.5/site-packages/trac/versioncontrol/api.py", line 73, in pre_process_request
self.get_repository(req.authname).sync()
File "/usr/lib/python2.5/site-packages/trac/versioncontrol/cache.py", line 70, in sync
cursor = self.db.cursor()
File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 78, in cursor
return IterableCursor(self.cnx.cursor())
File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 78, in cursor
return IterableCursor(self.cnx.cursor())
File "/usr/lib/python2.5/site-packages/pyPgSQL/PgSQL.py", line 2599, in cursor
return Cursor(self, name, isRefCursor)
File "/usr/lib/python2.5/site-packages/pyPgSQL/PgSQL.py", line 2718, in __init__
self.conn._Connection__setupTransaction()
File "/usr/lib/python2.5/site-packages/pyPgSQL/PgSQL.py", line 2510, in __setupTransaction
self.conn.query("BEGIN WORK")
OperationalError: no connection to the server
Attachments (0)
Change History (3)
comment:1 by , 16 years ago
| Component: | general → database backend |
|---|---|
| Description: | modified (diff) |
| Keywords: | pypgsql added |
| Milestone: | → 0.12 |
| Summary: | Blocked page → Problem with pyPgSql |
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Support for pyPgSql was removed in [8574].
comment:3 by , 16 years ago
| Owner: | set to |
|---|
Note:
See TracTickets
for help on using tickets.



Well, this seems to be a local administration issue, you've lost connection to your database, so it sounds like the database is down.
This problem might also come from too many opened connections, and hence be related to #8443.
Finally, this problem might be due to the use of pyPgSql itself, as we don't test it, we don't know how reliable this package is (and there are a number of reported problems with it).
So we recommend that you use psycopg2 rather than pyPgSql (see DatabaseBackend).
Hijacking this ticket so that we effectively disable support for pyPgSql in the code. That will remove one possible cause of trouble.