On Sat, 2025-04-19 at 12:38 +0000, sivapostg...@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
