From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | slyph(at)alum(dot)mit(dot)edu |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pg + perl + apache |
Date: | 2004-02-15 22:08:08 |
Message-ID: | 10987.1076882888@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Michael L. Artz" <dragon(at)october29(dot)net> writes:
> Anway, DBD::Pg throws random errors into my logs, along the lines of
> what is below (the lines beginning with SQL are debug statements from
> the script, and are the lines references by the DBD error.
> LOG: statement: SELECT session_key FROM session WHERE user_id = 101
> ERROR: current transaction is aborted, queries ignored until end of
> transaction block
This error cannot occur unless some other error occurred previously in
the same transaction.
My bet is that you are using some sort of connection-pooling mechanism,
and are being sloppy about handing off database connections from one
Apache thread to another. Specifically, some thread is getting an error
and then letting go of the connection without rolling back the failed
transaction on the database side. The next guy who gets that connection
from the pool fails as above.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2004-02-15 22:22:50 | Re: PostgreSQL Indexing versus MySQL |
Previous Message | Andrew Rawnsley | 2004-02-15 21:40:07 | Re: PostgreSQL License |