On 2025-04-19 13:06:27 +, sivapostg...@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 er
On Sat, Apr 19, 2025 at 6:06 AM sivapostg...@yahoo.com <
sivapostg...@yahoo.com> wrote:
> By any chance, if I get that statement, what should I do?
>
Read it.
What are the Steps (or documentation) to correct this issue?
>
>
Impossible to say until the statement is read.
David J.
Thanks Laurenz,
> it is 100% clear that an earlier statement in the same transaction musthave
>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 fr
On Sat, 2025-04-19 at 12:38 +, 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
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. ?
Happiness Always
BKR Sivaprakash
On Friday 18 April, 2025 at 04:50:52 pm IST, sivapostg...@yahoo.com
wrote:
If the query caused an error ..
If the query caused an error
Does it mean that other reasons might also be there?
Nevertheless, I'll check the log file to find the query...
Happiness Always
BKR Sivaprakash
On Friday 18 April, 2025 at 03:53:06 pm IST, Laurenz Albe
wrote:
On Fri, 2025-04-18 at 07:31 +, sivapost
On Fri, 2025-04-18 at 07:31 +, sivapostg...@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,
Laur
Thanks Laurenz,
Now I need to do 2 things.
1. Correct my application to catch errors and do either Rollback or commit.
This part is running smoothly from all other computers, so far. Nevertheless
I'll check that for any missing catch.2. Find the faulty entry and do rectify.
For the second p
On Fri, 2025-04-18 at 05:49 +, sivapostg...@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
Hello,
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 (wind
10 matches
Mail list logo
