From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | "sivapostgres(at)yahoo(dot)com" <sivapostgres(at)yahoo(dot)com>, Pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Error while updating a table |
Date: | 2025-04-19 12:55:12 |
Message-ID: | 05820f63079333ff7e475e61b44c8378a03aa8e2.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, 2025-04-19 at 12:38 +0000, sivapostgres(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | sivapostgres@yahoo.com | 2025-04-19 13:06:27 | Re: Error while updating a table |
Previous Message | sivapostgres@yahoo.com | 2025-04-19 12:38:49 | Re: Error while updating a table |