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 1os9sy-0005QX-7k for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 21:42:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1os9sw-00059r-74 for pgsql-general@arkaria.postgresql.org; Mon, 07 Nov 2022 21:42:26 +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 1os9sv-00059h-PP for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 21:42:25 +0000 Received: from mail-pg1-x52e.google.com ([2607:f8b0:4864:20::52e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1os9st-0005La-8M for pgsql-general@lists.postgresql.org; Mon, 07 Nov 2022 21:42:24 +0000 Received: by mail-pg1-x52e.google.com with SMTP id 64so11656570pgc.5 for ; Mon, 07 Nov 2022 13:42:23 -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=lX2mKy0w/+mFOxE5bVBn05nqWz/E/XkJQp9gBYY6eJg=; b=J3fgclWCXsX4ofXCMLhr2dvogKydoyxjNin9XTQGo8IrdsGc3jJhrcZ7n7nXQAOI/e +BgbChCBqP37fqfuSdI39A5RXiEfQCN3JqgnuGrYvChI6ifz6PWVSvSNIq2pHnkEywl7 Q93HJZNgRVfMIw8SkPgrvSgrusiLoNjhidWQr/eRO+huKRwhc8z/d74ipwUOcVsxhRqx fH5ipzX72NNWzkWTngpvp1xiGnpIsnjDyK1MPBhE1jxTp/Y053hhbI/uCEB3QwJniaKD Cxw84yzdq/vOElBO0sOZJCtfD9Io0x+8DCAumcThXQAhpnYoAT5heGtNKFcapI/iHhx+ mZFQ== 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=lX2mKy0w/+mFOxE5bVBn05nqWz/E/XkJQp9gBYY6eJg=; b=GaNJguy42HAi2m14cn04TMqgSHedtgj0XEGxMzddnXj7o7M5l8fP4V5H6gBC3mgEV/ UlL6AwTgQio9w/HpSroQoO63b5apB2S06sFVjY/vA8sDKMRIh8cxRf+i2SzF4v7fQqAf Ty79xfmLUaRdp2E1nktaavzpa7FiNThOUT6/rQij7ycXYcoqa3d2KFZLb2ZFWbOM8mI7 hcgH4fQEbhNgPi+KdOibQy11Fms+qfQk7P24UI01J6KbmcIakqvgtyldCbzd/5cOrOot Q2j6u9aVZ1a8M0v6ykUOKL8yzG/Leoa1M+3um5OrbL8bphN6L7229YxpaEnjvJ/X9cgp 0vlg== X-Gm-Message-State: ANoB5pl6sRqg3gBFsNQcG+lJZ2dNxC2f3gvE7ypsx+d3w2SwuPLOkwzO NddjWNuH8m+E3H5ZynhodUw3jxVQAFg= X-Google-Smtp-Source: AA0mqf4kCTWYekIye3/13gmtlDED3NqTtzEb7Yh9L0sqPcEcbNthaX/FjwxUgT1AYmDpJEJGYza9mA== X-Received: by 2002:a63:8f44:0:b0:470:7888:3371 with SMTP id r4-20020a638f44000000b0047078883371mr6481961pgn.157.1667857341648; Mon, 07 Nov 2022 13:42:21 -0800 (PST) Received: from [10.128.56.149] ([155.98.131.5]) by smtp.gmail.com with ESMTPSA id y15-20020a17090322cf00b00176d347e9a7sm5451199plg.233.2022.11.07.13.42.20 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Nov 2022 13:42:21 -0800 (PST) Content-Type: multipart/alternative; boundary="------------hFrsAGwXGi2T9sLjlWSNiIwA" Message-ID: Date: Mon, 7 Nov 2022 14:42:20 -0700 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 Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent 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. --------------hFrsAGwXGi2T9sLjlWSNiIwA Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/7/22 13:59, Brad White wrote: > > > > v9.4 has been EOL for 2 years 9 months. > > As I said, the next step will be to upgrade. > It would make sense to upgrade first, since "there have been some big > advances since then which make replication much easier" > But when we upgraded, the app stopped working. > So I'll need to go through and nail down which exact version causes > the issue and then see if we can get it resolved. > I have no way of knowing how long that will take. > So we're doing the replication first. Care to share some of the ways the app stopped working?  You might get a leg up on where best to remediate. --------------hFrsAGwXGi2T9sLjlWSNiIwA Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 11/7/22 13:59, Brad White wrote:

> v9.4 has been EOL for 2 years 9 months. 
As I said, the next step will be to upgrade.
It would make sense to upgrade first, since "there have been some big
advances since then which make replication much easier"
But when we upgraded, the app stopped working.
So I'll need to go through and nail down which exact version causes the issue and then see if we can get it resolved.
I have no way of knowing how long that will take.
So we're doing the replication first.
Care to share some of the ways the app stopped working?  You might get a leg up on where best to remediate.
--------------hFrsAGwXGi2T9sLjlWSNiIwA--