The error refers to the transaction being not usable anymore. So the error
happened erlier somewhere, but web2py traps it and lets the application go
on with an unsusable transaction. Probably a bug.
You can try to increase logging to log errors in posrgesql.conf and restart
the server, then
I have my system runing on sqlite at my dev environment, but when I push
to production which uses postres I get this:
Ticket ID
80.75.108.196.2012-05-28.05-45-56.74d0c90a-1a1b-4b60-8ba6-c13af5955bbb
class 'psycopg2.InternalError' current transaction is aborted,
commands
2 matches
Mail list logo
