2009-11-02 08:31:30 EST:user@host(48990):4562ERROR: current transaction is aborted, commands ignored until end of transaction block

Started by Chris Barnesover 16 years ago2 messagesgeneral
Jump to latest
#1Chris Barnes
compuguruchrisbarnes@hotmail.com

I hope someone can help me determine what is going on with my database.

We have released code this weekend to our application and I have switched over to my hot standby that has been tuned and modified to raid10. It is up and appeared come on line and pitr is running to the standby (ok)

We have also set up pgbouncer to handle all connections from applications to the database.

We are seeing the error ( 2009-11-02 08:31:30 EST:recognit@192.168.3.153(48990):4562ERROR: current transaction is aborted, commands ignored until end of transaction block )

consistantly in the database and I'm not sure if there was something left out of the code ( search indicates autocomit), or pgbouncer or putting the hot standby online, but with so many changes it's a guessing game.

It appears to be working in our RC environment.

Please help.

Sincerely,

Chris

_________________________________________________________________
Save up to 84% on Windows 7 until Jan 3—eligible CDN College & University students only. Hurry—buy it now for $39.99!
http://go.microsoft.com/?linkid=9691635

In reply to: Chris Barnes (#1)
Re: 2009-11-02 08:31:30 EST:user@host(48990):4562ERROR: current transaction is aborted, commands ignored until end of transaction block

On 02/11/2009 13:55, Chris Barnes wrote:

We are seeing the error ( 2009-11-02 08:31:30
EST:recognit@192.168.3.153(48990):4562ERROR: current transaction is
aborted, commands ignored until end of transaction block )
consistantly in the database and I'm not sure if there was something
left out of the code ( search indicates autocomit), or pgbouncer
or putting the hot standby online, but with so many changes it's a
guessing game.

Hi there,

This error is what you see if you (i) begin a transaction, (ii) execute
a query that causes an error, and (iii) try to execute further queries
in the same transaction. You'll continue to get this query until you
issue a ROLLBACK. - So my guess is that there's a problem in your
application.

Ray.

--
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie