Feedback-ID: i76984098:Fastmail
Message-ID: <eeceb0ae-3e3e-0a7d-2dd4-00032afff108@aklaver.com>
Date: Tue, 14 Feb 2023 17:35:48 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.2
Subject: Re: Quoting issue from ODBC
To: Brad White <b55white@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: 
 <CAA_1=93z4oEXKQ9GHtDkEQhEe5r39C8YSDMpwO8OHmSBreXw3g@mail.gmail.com>
 <CAA_1=90L6sd=+Jp1HVUoOQX8fHMotHRftfc_2Gs1L7syE678qQ@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: 
 <CAA_1=90L6sd=+Jp1HVUoOQX8fHMotHRftfc_2Gs1L7syE678qQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/eeceb0ae-3e3e-0a7d-2dd4-00032afff108%40aklaver.com>
Precedence: bulk

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@aklaver.com