From: | Klint Gore <kgore4(at)une(dot)edu(dot)au> |
---|---|
To: | Bayless Kirtley <bkirt(at)cox(dot)net> |
Cc: | "List, Postgres" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cause of error message? |
Date: | 2008-07-15 01:11:02 |
Message-ID: | 487BF926.5030509@une.edu.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)une(dot)edu(dot)au
From | Date | Subject | |
---|---|---|---|
Next Message | Harvey, Allan AC | 2008-07-15 02:59:41 | 8.3.3 Complie issue |
Previous Message | Mark Roberts | 2008-07-15 01:10:40 | Re: Cause of error message? |