Thread: Cause of error message?

On Mon, 2008-07-14 at 19:44 -0500, Bayless Kirtley wrote:
> An old app is giving a new error message. I query a table and make one
> update. Later I come back to query the table again and get this error:
>
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
>
> The error only occurs after I have made an update. As long as no
> updates, I can query multiple times. Can anyone give me an idea of
> what sort of actions or errors usually cause this error?
>
> Thanks,
> Bayless
>

I believe that this might be caused by a syntax error.  Do you have any
error handling code that might be hiding the error from you?

-Mark

Bayless Kirtley wrote:
> An old app is giving a new error message. I query a table and make one
> update. Later I come back to query the table again and get this error:
>
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
>
> The error only occurs after I have made an update. As long as no
> updates, I can query multiple times. Can anyone give me an idea of
> what sort of actions or errors usually cause this error?
>
>
It means that you have an open transaction and the statement before you
get this message failed.

e.g.
postgres=# begin;
BEGIN
postgres=# update bob set abc=1;
ERROR:  relation "bob" does not exist
postgres=# select version();
ERROR:  current transaction is aborted, commands ignored until end of
transaction block
postgres=#

You need to find which statement failed first and fix it or rollback and
have your app deal with the failure.  The postgres log is a good place
to start looking.

klint.

--
Klint Gore
Database Manager
Sheep CRC
A.G.B.U.
University of New England
Armidale NSW 2350

Ph: 02 6773 3789
Fax: 02 6773 3266
EMail: kgore4@une.edu.au

I have a very similar case, I am using erlang with postgres.
I began a transaction then make an insertion and then I got the error
"ERROR: current transaction is aborted, commands ignored until end of
transaction block" when i try any other query.

When i added the rollback line, It gave me another error which is "RollBack
Failed".

Does anyone know why a rollback fails in the transaction




Bayless Kirtley wrote:
>
> An old app is giving a new error message. I query a table and make one
> update. Later I come back to query the table again and get this error:
>
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
>
> The error only occurs after I have made an update. As long as no updates,
> I can query multiple times. Can anyone give me an idea of what sort of
> actions or errors usually cause this error?
>
> Thanks,
> Bayless
>
>

--
View this message in context: http://old.nabble.com/Cause-of-error-message--tp18456162p26811098.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

I have a very similar case, I am using erlang with postgres.
I began a transaction then make an insertion and then I got the error
"ERROR: current transaction is aborted, commands ignored until end of
transaction block" when i try any other query.

When i added the rollback line, It gave me another error which is "RollBack
Failed".

Does anyone know why a rollback fails in the transaction?

Thanks Alot,
Mai Fawzy


Bayless Kirtley wrote:
>
> An old app is giving a new error message. I query a table and make one
> update. Later I come back to query the table again and get this error:
>
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
>
> The error only occurs after I have made an update. As long as no updates,
> I can query multiple times. Can anyone give me an idea of what sort of
> actions or errors usually cause this error?
>
> Thanks,
> Bayless
>
>

--
View this message in context: http://old.nabble.com/Cause-of-error-message--tp18456162p26811115.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.