Message-ID: <02e2740edf821e2ce84773c83065b45e9be890cc.camel@cybertec.at>
Subject: Re:  Error while updating a table
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "sivapostgres@yahoo.com" <sivapostgres@yahoo.com>, Pgsql-general
	 <pgsql-general@postgresql.org>
Date: Fri, 18 Apr 2025 08:54:30 +0200
In-Reply-To: <1385521371.3160626.1744955370756@mail.yahoo.com>
References: <1385521371.3160626.1744955370756.ref@mail.yahoo.com>
	 <1385521371.3160626.1744955370756@mail.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/02e2740edf821e2ce84773c83065b45e9be890cc.camel%40cybertec.at>
Precedence: bulk

On Fri, 2025-04-18 at 05:49 +0000, sivapostgres@yahoo.com wrote:
> We use PowerBuilder along with PostgreSQL.
>=20
> PostgreSQL 15.7 (Ubuntu 15.7-1.pgdg24.04+1) on x86_64-pc-linux-gnu, compi=
led by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
>=20
> Suddenly, one system starts throwing an error while updating a record fro=
m PowerBuilder.
> The same update statement (window) works fine, when run from other comput=
ers.=C2=A0 Error
> occurs only when the statement is run from a particular computer.=C2=A0 T=
he SQL Statement is
>=20
> Update public.co_voucherseries_transaction_branch
> Set=C2=A0 =C2=A0 vouchernumber=C2=A0 =C2=A0=3D <new number>
> Where=C2=A0 companycode=C2=A0 =C2=A0 =C2=A0=3D '100'
> And=C2=A0 =C2=A0 branchcode=C2=A0 =C2=A0 =C2=A0 =3D '001'
> And=C2=A0 =C2=A0 accountperiodid =3D 1
> And=C2=A0 =C2=A0 voucherseries=C2=A0 =C2=A0=3D 'SERIES'
> And=C2=A0 =C2=A0 voucherversion=C2=A0 =3D 'version'
> And=C2=A0 =C2=A0 activestatus=C2=A0 =C2=A0 =3D 'Y'=C2=A0 ;
>=20
> The error is
> SQLSTATE=3D25P02
> ERROR: current transaction is aborted, commands ignored until end of tran=
saction block;
> Error while executing the query
>=20
> Through googling, I found that last transaction was not properly rolled b=
ack.
> The (Postgresql) Linux server will be shut down every night and re-booted=
 next day morning.=C2=A0 =C2=A0
>=20
> Don't know when this error has occurred.=C2=A0=C2=A0
>=20
> Now I need to rectify this error?=C2=A0 How to do it?=C2=A0 Any help is r=
eally appreciated.

You would have to improve the code quality of the application, which does n=
ot seem
to do correct error handling or transaction management.

That error means that the *previous* statement (or one of the statements ea=
rlier in
the same database transaction) has caused an error.  In PostgreSQL, that me=
ans that
the transaction is aborted, and the following statements until the end of t=
he
transaction will receive the error you experience.

So one of the following must be the case:

- the previous statement caused an error, but you didn't detect or handle t=
hat

- the previous transaction run on the same database connection caused an er=
ror,
  but you forgot to run ROLLBACK

Yours,
Laurenz Albe