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 1fdINv-0008KL-EB for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jul 2018 16:54:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fdINt-0005oB-BC for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jul 2018 16:54:33 +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 1fdINs-0005o4-UV for pgsql-admin@lists.postgresql.org; Wed, 11 Jul 2018 16:54:33 +0000 Received: from mail-qk0-x230.google.com ([2607:f8b0:400d:c09::230]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fdINp-0007dG-K0 for pgsql-admin@lists.postgresql.org; Wed, 11 Jul 2018 16:54:31 +0000 Received: by mail-qk0-x230.google.com with SMTP id u21-v6so14011820qku.2 for ; Wed, 11 Jul 2018 09:54:29 -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=evceJ9dVfLfF/HOhaPts7IesNsWwZjLrQD3YR8MwIxQ=; b=YI5vGmMF8xp2v1wBtSSL3lJgvQVXrc6U1HiVo3dgOiXikcxeyZjBlKjQZlAD76CphS bMwCRCVBWvscxbEoOl/WEfqgJwfSaGvucHJ1LXIojwulAnccIrg3VXeiCSYXxaPSv7qK Mkb3WfqKO0j6ptybzVgKCIc+SeV/1UfP7/BezL6EjDyyc2bXDjc9orw8nHQw9uvDGZXu J0VKumtJ/0esfRgh/ycyduuF9qHw478ptcs6Wt+8CTphRWnbeKiosgG2zpUark8G7c29 VySTtHf5R6GCbBhhfj4h8b/KUpUwe2KFu3Ibx8EE8pBhDGnOpaJQHTIT6iniCcDllnZb omzQ== 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=evceJ9dVfLfF/HOhaPts7IesNsWwZjLrQD3YR8MwIxQ=; b=F72ibG4jgGPGcotpECfV6Y5R0nLw0KLKc75WNQADCaBPGe/mb4U+5LfaXjV33GV1An qGALMysaCCsnb+XYrmIjHAW+I3eNtH4EpCjxeyDXGiPFNCu+Gt0/tKP3VMzGjlrf97+H J1bnK1OEw5sMBbKaE4KNh6wrQyLji3275xfZaD/bnv4zvhUTj/BEwNeNLD+FTBgEePV+ rwskSB3fmN5M9WEivAWmQolDVvhUqrB9Pz5PEsTGTwG8NlXv+rA2thRyDMDg0buqbZOt dFNDpA6TyLkP9hIuThsxox5dkkHcvvkPOMKqD/rqnrG7WMb0knjfGONwwG9mu3VoRLWD QPdw== X-Gm-Message-State: APt69E0zrxNY0Xa//C0HU1bZWxF3u20fdUvmIWZb98U4sj5YGdfU3Qv2 YZl6OZqO7D21K5xMae8iLj6cWA1z X-Google-Smtp-Source: AAOMgpdsKAi9QwIyzuYZI3c6Ln0rR3gpukQ2H5mKTeIVxiIPgseut577j+g4LVQ2eUR1YhAkRuWsSw== X-Received: by 2002:a37:16d1:: with SMTP id 78-v6mr27684800qkw.271.1531328068547; Wed, 11 Jul 2018 09:54:28 -0700 (PDT) Received: from ?IPv6:2600:1003:b00c:62bf:39a2:df92:53f6:5539? ([2600:1003:b00c:62bf:39a2:df92:53f6:5539]) by smtp.gmail.com with ESMTPSA id l73-v6sm24422991qkl.78.2018.07.11.09.54.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 09:54:28 -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: <20180711163633.GL23217@nighthawk.caipicrew.dd-dns.de> Date: Wed, 11 Jul 2018 12:54:26 -0400 Cc: David Morton , "pgsql-admin@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <8D4726EE-74E8-494B-9ED1-817EF2BB5E4B@gmail.com> <55998B04-BB01-45F9-B478-BCE1DA4E8E6E@eroad.com> <67BBE981-45B6-4CC8-BA3C-DF9210D46D8F@gmail.com> <20180711163633.GL23217@nighthawk.caipicrew.dd-dns.de> To: Michael Banck List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tried several branches including the one you specified. None of them mention= ed the newly revised PostgreSQL functions that were causing the compilation t= o break. I did manage to alter the code so it will now build with either 9.6= or the 10.4 instance. Was just sharing my experience as it was certainly br= oken prior. Sent from my iPhone > On Jul 11, 2018, at 12:36 PM, Michael Banck wr= ote: >=20 > Hi John, >=20 >> On Wed, Jun 27, 2018 at 03:53:20PM -0400, John Scalia wrote: >> 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 parameter PGVER. Adding a simple =E2=80=9C| cut -c1-2 to= that >> line allows the Makefile to run for 9.6 and 10.4, probably other >> versions as well. >=20 > (10.4 isn't a major version, it's the fourth minor/patch release of the > v10 major version). >=20 > If you don't have the `| cut -c 1-2' in your Makefile then you're > probably looking at the wrong branch, the pglogical master branch on > github is stale, you need (for reasons that escape me) the REL2_x_STABLE > branch. Or probably the 2.2.0 release tarball would work just as fine. >=20 >> There are compile problems, however, in several source files. I don=E2=80= =99t >> have the code in front of me, but one doing heap work calls >> replorigin_drop with a single argument, but that changed in V10 to >> need 2 args. Fairly easy to fix that one. >>=20 >> Another source calls ExecARUpdateTriggers, and its friends Insert and >> Delete, those signatures have changed as well, and I haven=E2=80=99t yet >> figured out how to alter pglogical for compiling these. >=20 > I assume those failues are addressed in the above branch/release as > well, but I have not verified that. >=20 >=20 > Cheers >=20 > Michael >=20 > --=20 > Michael Banck > Projektleiter / Senior Berater > Tel.: +49 2166 9901-171 > Fax: +49 2166 9901-100 > Email: michael.banck@credativ.de >=20 > credativ GmbH, HRB M=C3=B6nchengladbach 12080 > USt-ID-Nummer: DE204566209 > Trompeterallee 108, 41189 M=C3=B6nchengladbach > Gesch=C3=A4ftsf=C3=BChrung: Dr. Michael Meskes, J=C3=B6rg Folz, Sascha Heu= er >=20 > Unser Umgang mit personenbezogenen Daten unterliegt > folgenden Bestimmungen: https://www.credativ.de/datenschutz