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 1otYv7-0005lk-PL for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 18:38:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1otYv6-0007sE-KC for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 18:38:28 +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 1otYv6-0007s4-6t for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 18:38:28 +0000 Received: from mail-oa1-x30.google.com ([2001:4860:4864:20::30]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1otYv4-00042A-3t for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 18:38:27 +0000 Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-13b23e29e36so6268840fac.8 for ; Fri, 11 Nov 2022 10:38:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=tkSnlHCJmiBRZUegeo/wnmp6LBcOAgJn4T3r2OmR6Wg=; b=dBmewxjLyiqFqwWdcpANrqq0Mk7kpAMnEzbHWJmG51OiDYNi2BYl32AmSeGDPjRbTt w9NRMEDc2jIElskMEo6Lw/F0QI8iylA6oNcIJCEZG5HPrz/xIjtrNXyG2zYQfAvksO8R wNQVM0bBYr/bxO/otm44K2rqkYr3WsfrlJrmqredbhhmAeQOuQ2vK4wTJDMZbXn4lsrN KUj1RqZs1vHCiZY0ihpNMqhoTSE4XEO2TnGx2igKER2l2HZFFsjqSHI+t6TOYQP6qFLQ OOwbJDnz3bOneSuCUiBrcH9rQ0XJLQFkEIDHuCO1TGg3QJ4CQGskYDn6/zwxVrK/ubAf Iv8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=tkSnlHCJmiBRZUegeo/wnmp6LBcOAgJn4T3r2OmR6Wg=; b=OzkKp0c4aVxQ0T0ODWiiYwp3bGlHqQptLiIvyd+cxle2QK5h/gW+n9MS5uZZHDJT5B MyMcxMVaqBPsJID+9Vor7z/l9CnsnI9pyktXzFyEjR3BYNqRsY8rXqOUHXWFL5idvoaB viBJ64kQWy2Ul1JESYUj7eCte9L0EDOG22PT3WIEvGpu2qVgK8nI8aLYeyE63zuqpDDs 5SCBI10U+PyGYHjMEws/RmuKluFjeEaYk6OX7ZWKRZTi2khk1wxMllbvDqsuSeX5x8US T6BzR40IxaV4fxhb6QNTiclz2P8sXARD30lVZaNAQoaLMKA+DIBHOrbjN+c61iR1yTdV +GpQ== X-Gm-Message-State: ANoB5plByJNbjATIpHQDfwTEH2bUrfH0iRg6bQirCLIAf7d6R4UYYBy1 PawgK95WpmWf3pHSvxvBOBUMVBQs9NY= X-Google-Smtp-Source: AA0mqf7OIfnmXuVHpzaa/BUXe3g7RmP9rjKPg0lAcRqM+irVv7zm1CqzrBQDlTwSEUHmC7lj3IbHUg== X-Received: by 2002:a05:6870:d390:b0:13c:14f9:61b9 with SMTP id k16-20020a056870d39000b0013c14f961b9mr1554082oag.286.1668191904165; Fri, 11 Nov 2022 10:38:24 -0800 (PST) Received: from [192.168.88.10] (ip68-230-234-148.no.no.cox.net. [68.230.234.148]) by smtp.googlemail.com with ESMTPSA id 128-20020aca0586000000b003539686cb7bsm1070519oif.53.2022.11.11.10.38.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Nov 2022 10:38:23 -0800 (PST) Content-Type: multipart/alternative; boundary="------------nVDLeAxWzkh8d4qmhfbxSOR5" Message-ID: Date: Fri, 11 Nov 2022 12:38:22 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: Setting up replication on Windows, v9.4 To: pgsql-general@lists.postgresql.org References: <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com> Content-Language: en-US From: Ron In-Reply-To: <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------nVDLeAxWzkh8d4qmhfbxSOR5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/10/22 21:24, Brad White wrote: > On 11/7/2022 3:42 PM, Rob Sargent wrote: >> > Care to share some of the ways the app stopped working? You might get a >> leg up on where best to remediate. > I don't recall, as that was a few months ago. > > We are running MS-Access as a front end with Postgres as the back end. > It appeared to read and write data perfectly fine, but failed in the > business logic on the Access side where there didn't appear to be any DB > involvement. But switching to v14 caused it and switching away fixed it. > No obvious cause that I could see. Nothing in the application error logs?  What about the Postgresql error logs?   Or manually running the application queries? Anyway, try Pg 9.6.  Still EOL, but /not as/ EOL. -- Angular momentum makes the world go 'round. --------------nVDLeAxWzkh8d4qmhfbxSOR5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 11/10/22 21:24, Brad White wrote:
On 11/7/2022 3:42 PM, Rob Sargent wrote:
> Care to share some of the ways the app stopped working?  You might get a leg up on where best to remediate.
I don't recall, as that was a few months ago.

We are running MS-Access as a front end with Postgres as the back end.
It appeared to read and write data perfectly fine, but failed in the business logic on the Access side where there didn't appear to be any DB involvement. But switching to v14 caused it and switching away fixed it.
No obvious cause that I could see.

Nothing in the application error logs?  What about the Postgresql error logs?   Or manually running the application queries?

Anyway, try Pg 9.6.  Still EOL, but not as EOL.

--
Angular momentum makes the world go 'round.
--------------nVDLeAxWzkh8d4qmhfbxSOR5--