Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYBEG-0000Pj-P6 for pgsql-admin@arkaria.postgresql.org; Wed, 27 Jun 2018 14:15:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fYBEE-0004yv-NX for pgsql-admin@arkaria.postgresql.org; Wed, 27 Jun 2018 14:15:26 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYBCu-0000z7-4I for pgsql-admin@lists.postgresql.org; Wed, 27 Jun 2018 14:14:04 +0000 Received: from mail-qk0-x22f.google.com ([2607:f8b0:400d:c09::22f]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fYBCr-00071p-CB for pgsql-admin@lists.postgresql.org; Wed, 27 Jun 2018 14:14:02 +0000 Received: by mail-qk0-x22f.google.com with SMTP id a132-v6so1099920qkg.3 for ; Wed, 27 Jun 2018 07:14:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FQlKN0PxCUvWbIRg+60aOT3+RJOzGOG2mZqSOSRRTCY=; b=Bn7ssTDC321s0UFfW3Gao3hnmMul+owaUKJtv8AwOvekplF5Lcz5oiNM/sOjCHiepM PKELh1s0u3Fg4bGn94u4Os/sMmSVK5pExX4nBEIuV/BsYx6jPJekGNziFhUTMyu250Ou OUxS9Agb+9cX43HtQADS7cOWucbdtbv0XGV7P+14//AO3pVSNuvW6p2jebcGAcRSeh5z YNYVPOVPdM7UZ2iwrjHL3lSj9ce1SCl4qojyro1yxtGTzMf6UA5KcxOYBoLWZB1pNZGk An23D1nWv9ona2zKwmrq9HcKgU65uD5EOdPmuGovRvNrc+k6caADpmvSV8OvmeLw6GPP AFNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FQlKN0PxCUvWbIRg+60aOT3+RJOzGOG2mZqSOSRRTCY=; b=gguaQoF3Sfcrklom+7q3MEfu6giNPM/ANiHEIN85cCaHsxWhcSlkHUnmtvBtamGEm2 9EVlpTJwklL9DTAUM8ZoqlNMkEqmIcjRYV2oBcG8hdl4rpDfx+5zLMOo4hQMBEJd6mMo nynDBTg2VrySHtKnvIqm95oK6AJw/Uf1aG0Yp1xhVsGTCkfhNolbjiKuwcgbYONjiyM3 S+/oOx7BQGdg0nMLoYopAXTHWQPystI/NZDpzCIzrCbzH/XsK52il4q4elB1EuPK94m9 zVTFfHvgv3iZQqw/XGp4SoKU9nj5G8eo2GZPUpsNXFiGe6v4dqywTCsa+I5FjiOi9RBj Ngug== X-Gm-Message-State: APt69E1GH4ACdUCQtP6Kcqe+LVHfxk7i0H6xJ2lDQw9IBXY6r+hgQVIs 2sx5tIWVfvanUnd17+CTx0VNJoOo X-Google-Smtp-Source: AAOMgpc9wWEfnyjqirrrJffrnNP26zJZ/DUuOhz/RN1/5UrbeJWuv03V0jrWBAPEWEFx+GCakKGucw== X-Received: by 2002:a37:f44:: with SMTP id z65-v6mr5168791qkg.93.1530108839919; Wed, 27 Jun 2018 07:13:59 -0700 (PDT) Received: from ?IPv6:2600:1003:b024:95ed:892d:cbd5:f08d:dd91? ([2600:1003:b024:95ed:892d:cbd5:f08d:dd91]) by smtp.gmail.com with ESMTPSA id 61-v6sm2856802qta.69.2018.06.27.07.13.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jun 2018 07:13:59 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Upgrading 9.6.9 to 10.4 From: John Scalia X-Mailer: iPhone Mail (15F79) In-Reply-To: <55998B04-BB01-45F9-B478-BCE1DA4E8E6E@eroad.com> Date: Wed, 27 Jun 2018 10:13:58 -0400 Cc: "pgsql-admin@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <1C31B47D-0394-4349-A948-484AB8D09D93@gmail.com> References: <8D4726EE-74E8-494B-9ED1-817EF2BB5E4B@gmail.com> <55998B04-BB01-45F9-B478-BCE1DA4E8E6E@eroad.com> To: David Morton List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I managed to download the sources for the pglogical extension and successful= ly built it for my 9.6.9 instance. I then tried issuing a =E2=80=9Cmake clea= n=E2=80=9D, then reset the PATH setting, so it could find version 10, but th= e =E2=80=9Cmake USE_PGXS=3D1=E2=80=9D then failed with: pglogical_output_plugin.h:20:30: fatal error: pglogical_compat.h: No such fi= le or directory But I do see the required file in the compat10 sub directory, so why can=E2=80= =99t make find it? Sent from my iPhone > On Jun 26, 2018, at 6:47 PM, David Morton wrote: >=20 > Take a look at pglogical ... we've used it for 9.4 -> 9.6 and the same the= ories apply going to 10.x I imagine. People have used it in combination with= pgbouncer to achieve near outage-less upgrades. Some helpful links below: > https://blog.2ndquadrant.com/pglogical-logical-replication-postgresql-10/ > https://blog.2ndquadrant.com/near-zero-downtime-automated-upgrades-postgre= sql-clusters-cloud/ > https://blog.2ndquadrant.com/near-zero-downtime-automated-upgrades-postgre= sql-clusters-cloud-part-ii/ >=20 >=20 > =EF=BB=BFOn 27/06/18, 10:38 AM, "John Scalia" wro= te: >=20 > Hi all, >=20 > My employer is in the process of upgrading PostgreSQL, and they would l= ike me to make this happen without any real interruption of service. As I un= derstand it, 9.6 does not support the publish/subscribe model like 10.4 does= , but logical replication is the basis of that model. So, does anyone have a= ny suggestions for how to implement the receiver side on a 10.4 server? Or c= ould you at least point me to some sort of how-to page? >=20 > TIA, > Jay >=20 >=20 > Sent from my iPad >=20 >=20