Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fYGVL-0003zi-US for pgsql-admin@arkaria.postgresql.org; Wed, 27 Jun 2018 19:53: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 1fYGVK-0006KC-5A for pgsql-admin@arkaria.postgresql.org; Wed, 27 Jun 2018 19:53: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 1fYGVJ-0006K5-OL for pgsql-admin@lists.postgresql.org; Wed, 27 Jun 2018 19:53:25 +0000 Received: from mail-qk0-x244.google.com ([2607:f8b0:400d:c09::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fYGVG-0006Ge-R6 for pgsql-admin@lists.postgresql.org; Wed, 27 Jun 2018 19:53:24 +0000 Received: by mail-qk0-x244.google.com with SMTP id b66-v6so1730835qkj.1 for ; Wed, 27 Jun 2018 12:53:22 -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=r41JDW4MDaoe+Zbz63kgzxS45Mfr6fq3OCJ2t7J6DNo=; b=VQHXAyYpZQBd0Lb7NRCwTtdzjkr+2JksQohAq8gs5nA+hAG/Qk8+qqiRc4SKZ4OPBO 5UXw0zJtAU+caeU6u4Ft1QFJ8KZtOzQMg6tQd0jThSLSir6aqVR4cX80w0lYCLgJHFNi 64CNoFJ0BN9CM2X+VHKoaeM/Zi5WC9ja6cPHQle/GvALwJfUC7TrY00pd7XJBr91juRJ fxoZCPBZbaf+87RtUZNh9+5JWPDTWtEb7S+CvNGB+454iN1/Htp/2QjnAHgY8gRFYrr2 EhU4qJF+bSor/EW38fuwpW09vLwFOKCTdH3JVYBkh8bKqts1kep5LrNsVkLT6pyqCHnA lEqw== 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=r41JDW4MDaoe+Zbz63kgzxS45Mfr6fq3OCJ2t7J6DNo=; b=i9jDD1g8opCZGA6UGsPD2EjqkgA6hIT+Rj192Es6NqDf4zevf+wgtm6EHa7Krj5iOM wA0PO7qyLWY2v8UI95udFpOV8IxVT2r5/KbGCPRbmhSLlcy7YjI0Xub/wLoIolEXTdZZ +Q9f+UpGAN4e3s6S515BiRTSy+N2gf+SxXydDjUctzr71ZV+ocBVeS2qNF3QIHuZxhrr +SxIiabbX97DP35lwnzS+S6Roh11hWZ9cj8D/k6QM0WI6nx2uYI5sZxfXwEwSgbcGu73 2pYgxYx3IMMIaJlbsXedrTbHGM00ivS8ggx30oDSgeHn6z27Mz+WfwTTGen+vKjznPdl 5ECQ== X-Gm-Message-State: APt69E32o2tWHnbh/wwboBZRkYtI3XgrpdRF2lfSXNO8zXw1u9NJayju lL4N2ATDjDVyZJcMBj4sOVErqX7b X-Google-Smtp-Source: AAOMgpff7i/tPbMbQnx3dZOgpNsoa7VN5Oqg5ATm3THw/mm4OKCPnSsd6RGqa8h1RJ7b4/RVFkuIpg== X-Received: by 2002:a37:c91b:: with SMTP id q27-v6mr6524078qki.397.1530129201434; Wed, 27 Jun 2018 12:53:21 -0700 (PDT) Received: from [192.168.1.152] (pool-100-16-117-12.bltmmd.fios.verizon.net. [100.16.117.12]) by smtp.gmail.com with ESMTPSA id y36-v6sm4435064qth.15.2018.06.27.12.53.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jun 2018 12:53:20 -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: iPad Mail (15F79) In-Reply-To: <55998B04-BB01-45F9-B478-BCE1DA4E8E6E@eroad.com> Date: Wed, 27 Jun 2018 15:53:20 -0400 Cc: "pgsql-admin@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <67BBE981-45B6-4CC8-BA3C-DF9210D46D8F@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 Ok, I figured out why the Makefile is broken for pglogical for PostgreSQL V.= 10. The pg_config utility returned 10.4 for the line setting Makefile parame= ter PGVER. Adding a simple =E2=80=9C| cut -c1-2 to that line allows the Make= file to run for 9.6 and 10.4, probably other versions as well. There are compile problems, however, in several source files. I don=E2=80=99= t have the code in front of me, but one doing heap work calls replorigin_dro= p with a single argument, but that changed in V10 to need 2 args. Fairly eas= y to fix that one. Another source calls ExecARUpdateTriggers, and its friends Insert and Delete= , those signatures have changed as well, and I haven=E2=80=99t yet figured o= ut how to alter pglogical for compiling these. If anyone reading here is from 2nd Quadrant,I=E2=80=99m curious if this is a= ctually being maintained. I did post these as an issue on github. =E2=80=94 Jay Sent from my iPad > 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