Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pS4GU-0006zB-9X for pgsql-general@arkaria.postgresql.org; Tue, 14 Feb 2023 22:59:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pS4GS-0004Ax-CZ for pgsql-general@arkaria.postgresql.org; Tue, 14 Feb 2023 22:59:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pS4GS-0004An-1X for pgsql-general@lists.postgresql.org; Tue, 14 Feb 2023 22:59:08 +0000 Received: from mail-yw1-x1130.google.com ([2607:f8b0:4864:20::1130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pS4GL-0004Xc-M4 for pgsql-general@lists.postgresql.org; Tue, 14 Feb 2023 22:59:07 +0000 Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-52eb7a5275aso217394897b3.2 for ; Tue, 14 Feb 2023 14:59:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=zHbRQYGXq4e3P+z1RoDF6QSVckKiHZKl+BszmgaDXpI=; b=EiqxmoY/Jwou2iey++0LRoBAzcRSAPXgj631IczYeCSMK7FERj8CTRDA77NAt/sE4U 7iA3A24UgP9TJKko0EK7DW+CrkpXIzDM9a6rTNy4Lm6nm7X2xrxR+PpC0uoENSSv04Tw 6q3uN3wLZzyfuDaS1PWzB9QPSbiTYHnycY94WmDn4XNoCEcqsStPQ1YluG9iUsj3IB2O r5ywvTWpkjG88s7E2tTlKOoO7EymPiPhq4Nl+dsigscJCSuvcd9sNa2HlcSlvvOuPPxV vpEou+DOqsaN1O83PBJWeWnGkgoi6wOZ+S48QDMQ/urrPTjgIbp7OUVdtc2qTSGWkQMC LCig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=zHbRQYGXq4e3P+z1RoDF6QSVckKiHZKl+BszmgaDXpI=; b=YGokTZ7UwyyFhFKZ3bsYq/J+CEKH9Wm6DLfEbupvgwuz3yBtbA7gOZeXWP42tqUonG qJMANMZsRiGGRhiCpEY7RTEwMYGt9/yRR+kw43Kyx5nHRilHjOGm6/JONUt/Ga75fo4F Jx35ARwRIdm6BAlhvjMfi44V6ReYm4c4UIifmgPFpu6RB0R0CSiqDAozcbUaNpF2hMuz ZxLAkO624x26TCFRJ5mMgcXujiVjqZvIMTC9DWjtHy7nYIqwrjbHVEbJCAP/x/8pPljz CPOf/m/4bfIH5hCbz6xxgWFVDkjMj4qkq3uDYQParGtp+kZZ3e+4+WsBEMPNV4qUpv0M dMpA== X-Gm-Message-State: AO0yUKXnj9bbgElDKdK3wXziaHGtAkRlApRjunYP15v9DhHUryjBbOZr QiuKyoPPEInjjt2j4xt9kwpdnqAKCwyxXoQx3PBXo+tV96o= X-Google-Smtp-Source: AK7set+M1RxfaDEJ16LSHXi31tfN0z1rRIWwXLfFm5EHDqwI1HNTJYTjJgz7j3thV7pWYbioH2Bcjz3i23aaYy3zfUc= X-Received: by 2002:a81:c214:0:b0:52e:ebba:5f90 with SMTP id z20-20020a81c214000000b0052eebba5f90mr22564ywc.275.1676415539777; Tue, 14 Feb 2023 14:58:59 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Brad White Date: Tue, 14 Feb 2023 16:58:48 -0600 Message-ID: Subject: Re: Quoting issue from ODBC To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000be9b6205f4b0e8e6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000be9b6205f4b0e8e6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > 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. 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. =C2=AF\_(=E3=83=84)_/=C2=AF On the other hand, there are some real errors in the log. I'll put that in another post. Brad --000000000000be9b6205f4b0e8e6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Are these UPDATE's actually nece= ssary?
> In other words has nobody noticed a problem with the data ov= er that time frame?

I don't know w= hat 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 erro= rs never show up in the Access log.
That means that Access didn&#= 39;t get an error back.
Further, I have evidence=C2=A0that the=C2= =A0values are actually getting updated.
The financial=C2=A0balanc= es are all correct.
Issues that were closed are all closed, etc.= =C2=A0
Even though the Access log says the statement=C2=A0was onl= y run once and Postgres says ERROR, I see no other evidence of it.
I can't fathom how that can happen.

=C2=AF\_(=E3=83=84)_/=C2=AF

On the other hand, there are some= real errors=C2=A0in the log. I'll put that in another post.

Brad
--000000000000be9b6205f4b0e8e6--