Interestingly enough, I can then go ahead an view the error ticket,
using the admin interface, which allows me to log in with password,
edit, view files, etc.
I've checked the various .table files and they seem to be OK, so I'm
not sure why web2py is trying to re-create the tables, unless it is
mis-interpreting the failure of a previous transaction (the first
postgres error, about there already being an uncompleted transaction)
as meaning the table does not exist.
So, I'm thinking that this really may be a case where somehow web2py
is trying to nest postgres transactions, failing to complete a
transaction (";") before starting another, or just misinterpreting an
underlying postgres feature.
I suppose this should all be clear, if I were to spend more time
reading the web2py code. Sorry I have not yet managed that.
-wes