public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Brad White <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Quoting issue from ODBC
Date: Tue, 14 Feb 2023 17:35:48 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA_1=90L6sd=+Jp1HVUoOQX8fHMotHRftfc_2Gs1L7syE678qQ@mail.gmail.com>
References: <CAA_1=93z4oEXKQ9GHtDkEQhEe5r39C8YSDMpwO8OHmSBreXw3g@mail.gmail.com>
	<CAA_1=90L6sd=+Jp1HVUoOQX8fHMotHRftfc_2Gs1L7syE678qQ@mail.gmail.com>

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
[email protected]

view thread (14+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Quoting issue from ODBC
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox