On 2/14/23 14:58, Brad White wrote:
> Are these UPDATE's actually necessary?
> In other words has nobody noticed a problem with the data over that
time frame?
I don't know what to make of it.
I had the same question you did.
I now have proof that these hundreds of errors are not an issue.
The postgres logs in pg_log clearly show an error, but the errors never
show up in the Access log.
Then either:
1) They are not coming from Access.
2) Or indirectly from Access, which kicks off some other code that is
not logged.
In either case they seem to be surplus to requirements. In other words
cruft that is not actually relevant to the application.
That means that Access didn't get an error back.
Further, I have evidence that the values are actually getting updated.
The financial balances are all correct.
Issues that were closed are all closed, etc.
Even though the Access log says the statement was only run once and
Postgres says ERROR, I see no other evidence of it.
I can't fathom how that can happen.
¯\_(ツ)_/¯
On the other hand, there are some real errors in the log. I'll put that
in another post.
Brad
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
