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 1otKeH-0005y3-V8 for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 03:24: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 1otKeG-0000Oa-F4 for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 03:24:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1otKeF-0000OQ-UE for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 03:24:08 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1otKeC-0000gn-4e for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 03:24:06 +0000 Received: by mail-oi1-x233.google.com with SMTP id n205so3885168oib.1 for ; Thu, 10 Nov 2022 19:24:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=lxn/puMqOyWxjC5E/FpoalH6EKvtYlvu4Nm2PfcdoxA=; b=G9O9Ir6dh8LGx0awe4O2U69bxfOFAA3VwZEIC8+vHqZ7byvkaJ6SjfplSNok/p7Tyz O3h259LV5gMf9FjlIqfms0hX5eS8phXcJ/Dn5sgPJofifMK39jlNum+AI2ib9AVCxdxp ax5mNuAiw7OZ16bpGSbtd9SN2MqrHmIwZnGd6z6CwG0vrP+tab4zbZcCKkRS68xf8ma0 KLjmUxyA3J4HimlQyS9Po0LUcr3PEMwBoSEjvu8atAuUo7dqL2EFOTLrV3vShT7wKQPh oi3Z6VqcXKiwBGmhZDa6RFX7e9Oawpjg4W+CLaj0QNIajS/ESHqpT6stWQ7U4YCu1rpo QKyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=lxn/puMqOyWxjC5E/FpoalH6EKvtYlvu4Nm2PfcdoxA=; b=hlmGMYZSFyfLSPPMhvdNcZgTqNdaLQdBFLy4gBvkex+ABLKCTuhXfsp3S42Ie1vO1W OxHYwo+7Mgzw9QLfoO/iR1V/KntZfVpfMEcALBi4jV9W7c4GDyS/Cig2fMfbrnxoV0Ey //yZBcRWdjF86I6gFZPDJn6u4plbDN/e7Op5kRvb03b8l+iyTqV5nWK0CbL6KAY2hqve B4du3wel6xM7jUGo+mew8JLOX58zXufsvhaGXO+1d0Awvd4+b4fzdUL3Wlv4gTbjzkeg qIl+Fsx3yyaTOypCZwWc43T0Vk4lIzrWKpD7PR4+YtYMZ0HcUvcAYH155d5qNWmmwkm6 hrjg== X-Gm-Message-State: ANoB5pn6S4lmIzDa8Lx00WVbaRO2hsrO2lsr58XboowayvUcdaYKbd5i 06DGjTQyB+o8ecnQu0twqVFCoqUD7hI= X-Google-Smtp-Source: AA0mqf4Z5hJRaex4DMIUmS5hQBPZ+myAXv25RPKURmAfciK8QbTroJw5BkyeYUPE5kN7Xq2xqryZUg== X-Received: by 2002:aca:3883:0:b0:35a:9331:f988 with SMTP id f125-20020aca3883000000b0035a9331f988mr2108339oia.69.1668137042866; Thu, 10 Nov 2022 19:24:02 -0800 (PST) Received: from [192.168.254.71] (h244.184.30.69.dynamic.ip.windstream.net. [69.30.184.244]) by smtp.gmail.com with ESMTPSA id r7-20020a056870580700b0011bde9f5745sm725046oap.23.2022.11.10.19.24.02 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Nov 2022 19:24:02 -0800 (PST) Content-Type: multipart/alternative; boundary="------------RgD0DvdPxD3qw0Dgj5GECEnF" Message-ID: <0d0361ba-223d-7e4b-1f44-337cfedab3b9@gmail.com> Date: Thu, 10 Nov 2022 21:24:02 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.0.2 Subject: Re: Setting up replication on Windows, v9.4 Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Brad White In-Reply-To: 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. --------------RgD0DvdPxD3qw0Dgj5GECEnF Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. As written, switching databases was very time-consuming. Since then, I've rewritten the app so that the network admin just changes an INI file that the app reads on start up. If there is a change, it switches all the tables over in about 15 seconds. We wanted that ability anyway in case we ever needed to switch to using the backup server. Now, I am working on getting replication going. Next up: back to upgrading. But, since you ask, I'll post here when I get back to that so y'all can follow along as I narrow it down to a specific version. --------------RgD0DvdPxD3qw0Dgj5GECEnF Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit


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.
As written, switching databases was very time-consuming.
Since then, I've rewritten the app so that the network admin just changes an INI file that the app reads on start up.
If there is a change, it switches all the tables over in about 15 seconds.
We wanted that ability anyway in case we ever needed to switch to using the backup server.
Now, I am working on getting replication going.
Next up: back to upgrading.

But, since you ask, I'll post here when I get back to that so y'all can follow along as I narrow it down to a specific version.
--------------RgD0DvdPxD3qw0Dgj5GECEnF--