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 1fdHdk-00060w-HZ for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jul 2018 16:06:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fdHdj-0008Ss-0g for pgsql-admin@arkaria.postgresql.org; Wed, 11 Jul 2018 16:06:51 +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 1fdHdi-0008Sl-MB for pgsql-admin@lists.postgresql.org; Wed, 11 Jul 2018 16:06:50 +0000 Received: from mail-qk0-x243.google.com ([2607:f8b0:400d:c09::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fdHdf-0006ay-9Q for pgsql-admin@lists.postgresql.org; Wed, 11 Jul 2018 16:06:49 +0000 Received: by mail-qk0-x243.google.com with SMTP id z74-v6so13886204qkb.10 for ; Wed, 11 Jul 2018 09:06:46 -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=0tvU2IP//cfd76QCJI/gJ5TY4VRhX1EhI9HZr5Ozn4k=; b=UoodxRk8bHzoBt704pbFWXwKO1LG/Eiu96irwGPOnYLTxgPDdq1SDmsyY8LvKZl/KD WVcEEsPvaIQKJE/7mAAeiJYAQfbk/Ybd7o8MUTYnaCD4cEvqn2UVNR6yC6zwXTwNgwrg Vcd1Y9QlIQPnTlSy2iSakKMbtmj+3fFZ8L35xCQ7M2Lp1LlNDANnLesbCu721b1POvLf zZhazGq1Z2k50EMsbQGolufNlYkLRkBAyKsYLzxpl7pYhdgtT1nRpOtm4v0EVuITO7Yu OUp4MpIWawEYuzbQ6LQkbmRFXf/U8+mII55Swu4hlU3cphufDoDACVz+fVBuk98XNR9O tLEw== 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=0tvU2IP//cfd76QCJI/gJ5TY4VRhX1EhI9HZr5Ozn4k=; b=RcBhsX0AF4+wKKXhtBiMbgZwhplcTPSROASCnjWxy4LLRsuJFwDX7DV0fxMJkOroZa Ri2KnJql3ZAMdmucMtRgvpGEpLzwFhB878kIwA7QMHFeWFWW0yCVsvWi3qcElMlvEinY qi1CCLj061A0zsto7t+rXzmNEauCVaDCw81xQIFat3sYOtdwk8pYGaKnjFQK6Tat9eTf sYhbaWoRNj/iOvIwqyY1GahNyh5YFIodntqj8MWMflu4hXnp7LKQobdnc1zOiPE/8To4 5C9RrOK44Ny+XEbxAljDyv6MEoR33udbXg+uzg2uaROycKpUhfebm+EBuy/ARrgJ3yHs ga8Q== X-Gm-Message-State: APt69E0disepehxjwvkoQ85ouxS/5AX7m4hUvl7g0MxZmtnD//Y7Lv+S kPwEyJkkpg5fH4HhDaOaA6kxpTBz X-Google-Smtp-Source: AAOMgpfDe1dFbw2RgYHzJygF3TPQR+KIUcslBuf/OEcgrclyNlWRRV6ShjTtRBMC59f/XJWiqG3Z4Q== X-Received: by 2002:a37:7a46:: with SMTP id v67-v6mr25688586qkc.188.1531325205792; Wed, 11 Jul 2018 09:06:45 -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 s6-v6sm6276331qkb.26.2018.07.11.09.06.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 09:06:45 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: upgrading postgresql cluster(3 nodes) to v10 without DOWNTIME From: John Scalia X-Mailer: iPhone Mail (15F79) In-Reply-To: Date: Wed, 11 Jul 2018 12:06:44 -0400 Cc: pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Mariel Cherkassky List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk You can do this with the pglogical extension. I asked a similar question abo= ut a week ago. =E2=80=94 Jay Sent from my iPhone > On Jul 11, 2018, at 10:38 AM, Mariel Cherkassky wrote: >=20 > Hi, > I have in my company 3 postgresql nodes(v9.6) that are configured as one p= rimary and 2 slaves. The repmgr tool is reponsible for the replication. I wa= nt to upgrade all the nodes to version 10.4. I know that PostgreSQL doesnt s= upport streaming replication between different major versions. Did someone t= ry this kind of upgrade without having any downtime ? >=20 > Thanks , Mariel.