Re: psycopg2 multiprocessing problem

On Sun, Feb 7, 2010 at 6:17 AM, Federico Di Gregorio <fog-NGVKUo/i/[email protected]> wrote:

> On 05/02/2010 22:12, kevin wrote:
> > when making db queries using psycopg2, web.py on processes spawned by
> > multiprocessing i get this error:
> >
> > http://pastie.org/811424
> >
> > InternalError: current transaction is aborted, commands ignored until end
> of
> > transaction block
> >
> http://stackoverflow.com/questions/2209560/internalerror-current-transaction-is-aborted-commands-ignored-until-end-of-tran
>
> This is not so bad. It is just that some query was wrong and you didn't
> call rollback() before issuing other queries. I suggest you enable query
> logging and check the PostgreSQL log for errors. Then, if the wrong
> query was NOT written by you, i.e., if psycopg somehow sent to the
> backend a wrong query, please post the code and SQL here so that we can
> fix the problem.

i am getting this error message in pg_log log directory

http://pastie.org/813651

i do not think there are any error in the queries [select, insert/updates] i
am doing, because if i switch to threading instead of multiprocessing i dont
get any error at all. but i want to use multiprocessing.

_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/[email protected]
http://lists.initd.org/mailman/listinfo/psycopg