Thread: Re: Error while updating a table

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

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

That error means that the *previous* statement (or one of the statements earlier in
the same database transaction) has caused an error.  In PostgreSQL, that means that
the transaction is aborted, and the following statements until the end of the
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 that

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

Yours,
Laurenz Albe

On Fri, 2025-04-18 at 07:31 +0000, sivapostgres@yahoo.com wrote:
> For the second part, how to identify that culprit query?

If the query caused an error, and you left "log_min_messages" at the
default setting, the error and the statement that caused it should
be in the PostgreSQL log.

Yours,
Laurenz Albe

On Sat, 2025-04-19 at 12:38 +0000, sivapostgres@yahoo.com wrote:
> So far, I couldn't find the query that caused the error.   Is there any way to unlock it?  
>
> Re-start, Format and fresh install of windows, etc. ?

On Windows you have to reboot, bow three times toward sunset,
say a prayer to Bill Gates, then reboot again.

No, seriously: randomly messing around with your machine rarely ever
gets you closer to a solution.

If you get the error

  current transaction is aborted, commands ignored until end of transaction block

it is 100% clear that an earlier statement in the same transaction must
have got an error.  Write your application so that it logs *every* error
that comes from the database, then you are sure to catch that error.

Also, if "log_min_messages" is "warning" (the default) or "error", you
will find the error in the PostgreSQL log.  That's all I can say to you.

Yours,
Laurenz Albe

On 2025-04-19 13:06:27 +0000, sivapostgres@yahoo.com wrote:
> Thanks Laurenz,
> > it is 100% clear that an earlier statement in the same transaction must
> > have got an error.  Write your application so that it logs *every* error
> > that comes from the database, then you are sure to catch that error.
>
> There is an option to log every sql statement that's executed from the
> application.  Unfortunately, that option was not set at that time.

You don't have to log every sql statement. Just the ones which cause
errors. As Laurenz mentioned, that happens automatically with the
default settings.

> Even I enable it now, I can't figure out that error.

Just search the logs for the string "ERROR".

> By any chance, if I get that statement, what should I do?

1) Read the error message.
2) Figure out what caused the error
3) Fix the problem

        hjp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"