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 1q1TWw-0000yS-JX for pgsql-general@arkaria.postgresql.org; Tue, 23 May 2023 15:02:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q1TWv-0005W3-EL for pgsql-general@arkaria.postgresql.org; Tue, 23 May 2023 15:02:29 +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 1q1TWu-0005Vu-RN for pgsql-general@lists.postgresql.org; Tue, 23 May 2023 15:02:29 +0000 Received: from outbound5d.ore.mailhop.org ([100.20.105.3]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q1TWs-001TOZ-6y for pgsql-general@lists.postgresql.org; Tue, 23 May 2023 15:02:27 +0000 ARC-Seal: i=1; a=rsa-sha256; t=1684854145; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=RA28AxaLMBLcCE93Q89X3ezSHSHve0cKIuYoI+MdqcXGZKgA+SfMFuKOd3TLyAu7Q+RFLvNcSKq7v oe8U1U9oCytlbNoxDRIMtz2dwwcKyTJEOr1LWJpaIuFlvR2rJOQ6eEHCwdaTZEeWRRmufd8FuHoUaA MHN3j2CyDYOUtL1Ns1cfHc8YIKw4rMCFgYU0tuElYOYUFW/ylY9qJWviUTQkVY3UKIwH9k+pQIE7x0 iGdo1Bk5RcNJsCNVEOAQjLRZj1Kt0T+lk6lle669yQPMNQOPpOGobH+Me3FumYoRspqSSiuMkDOhFZ n5m6IC3MWmbqAk0rBJffR+9H5OIxnDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=mime-version:content-type:references:in-reply-to:date:to:from:subject: message-id:dkim-signature:dkim-signature:dkim-signature:from; bh=t9ruE0FYBsvI9yJTXxkenJu2XRy4pjjjt1RgnUhgZic=; b=kBOQePNREArIMmrwIr0FVxyJ6fa3vKhAfN2LuUm/d70n7+/lSX+DAsxuAj0zRKgTpAwvD+Z/YXm2P 9Lq0Lo1AzZZTYhYOH6/lML51Am80aFIvA6KXmCXvZZDZv0vAWnQ+nEbiNazoUcFWU8aoa5SWRN6K4N cF09t0XVC7+Df/5OvFPgTGPpuoOQBe9x2AaLCJqjns3Ftrxhi+JC57O+R3QooFh+fNzG5oiBJ0rv96 yM9rN9QSCzRXXHwlMus/JBgWlv3ACKXfAmu2BPYNsXFc0LFsPA4XK0TCc4uEjZK29e91meXGwD8MjN SmAQzY4nQrQCZalW91k+3m8CsyZnc8Q== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=pass smtp.mailfrom=lists.simkin.ca smtp.remote-ip=172.105.109.24; dkim=pass header.d=lists.simkin.ca header.s=athena header.a=rsa-sha256 header.b=GFxf6RhE; dmarc=pass header.from=lists.simkin.ca; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lists.simkin.ca; s=duo-1610662143981-d3c4c825; h=mime-version:content-type:references:in-reply-to:date:to:from:subject: message-id:from; bh=t9ruE0FYBsvI9yJTXxkenJu2XRy4pjjjt1RgnUhgZic=; b=NTyGcYdnE0i4TVKZ55OUNILNewHpJvUY6HhVPqMB7pFlViUv+qe7RToXCyedt2Bop99K1FKb93f2K G+j14JfOrK6dzAmPwwpE42TZPFPxENI5GSuL9FNRIUL4nycgLQuURRxgJBuqry6SYiLzU4YtfTGNeY rq+FcKk1awWzE3j8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=mime-version:content-type:references:in-reply-to:date:to:from:subject: message-id:from; bh=t9ruE0FYBsvI9yJTXxkenJu2XRy4pjjjt1RgnUhgZic=; b=ZULpvA9ocXs+q4fzFBaGvTLHpWyjiKIr/WoJfo9WaGpDiNcWhnyttYUAn4Zz90qOOT7I6pb3rkqRH QDUDWLFvxhiaGT/HJ7VJtkM+2LhsiRmaFGGLbUr5RYbxA7XKe/ixUQ6YK2i+TX989s/Brsqx4rrTJL 02JcBfpeNSZ+IpCXhdc9ATtBM0U+m7TbcrHlVYOKUbyEqUmbIcpk22iCFegr6uNHeuxNwCDcMHoHAm IAz2mapITVes+YBS8GavL9PMHECe3WeRrRDCszJP7Yg3A0VZOFJEgY96nDKirYQ1N+mcIYgsELqQAA O6uRRKIs/2zib0FaZRzQSFc+EmtrYWA== X-Originating-IP: 172.105.109.24 X-MHO-RoutePath: c2lta2lu X-MHO-User: d24aa912-f97a-11ed-8626-d1581f149e9f X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Mail-Handler: DuoCircle Outbound SMTP Received: from athena.simkin.ca (athena.simkin.ca [172.105.109.24]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id d24aa912-f97a-11ed-8626-d1581f149e9f; Tue, 23 May 2023 15:02:24 +0000 (UTC) Received: from skynet.simkin.ca (d154-20-71-66.bchsia.telus.net [154.20.71.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by athena.simkin.ca (Postfix) with ESMTPSA id 88363C6B877F for ; Tue, 23 May 2023 08:02:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.simkin.ca; s=athena; t=1684854131; bh=ZeQHtVQswaV0PlW3aQMJMHjpV5fUQLBwfP+RMYLrlYY=; h=Subject:From:To:Date:From:To:Subject:Date:Reply-To; b=GFxf6RhEfgl3nkokdNEcdrXTeIDE+fGqTCrcxaee2FfP3LGvr0K47cIpf7kZLr+Xu ffoizUGFeubMtDpLXEsC03ycfb0EJd+gJPK+qL8bHB6T5PCT/L7LQrqLZHC3ScT0r5 V5ppu8EkqhrdKZ72hg2qZtQdQ9ZE5zrSU+2geajkYqssQHVfjrthjXUpyv5A1dvGt+ 2bdpurd0Paff8envtLFnuHBrHpPmbFs2uXPqxGN4wvq9htWtcfpSSLvALciAnpJtS6 H/XV+8eoMO5qZ8NLXZ3NwfrY8Y3CzaJuyzyR8xrT27olFJaJPdZfNv3sHmj/tVOZzc p4xicas+CVVrg== Received: from skynet.simkin.ca (skynet.simkin.ca [IPv6:::1]) by skynet.simkin.ca (Postfix) with ESMTP id 70D8E22D50FDA for ; Tue, 23 May 2023 08:02:20 -0700 (PDT) Message-ID: <327a821bc88b41fc15cc04f18695e2d20d874312.camel@lists.simkin.ca> Subject: Re: Trying to understand a failed upgrade in AWS RDS From: Alan Hodgson To: pgsql-general@lists.postgresql.org Date: Tue, 23 May 2023 08:02:20 -0700 In-Reply-To: References: Content-Type: multipart/alternative; boundary="=-l/Qmd6PDtTIm32zpIoyp" X-PGP-Key: fp="EF82 6F8D A3BA A096 FFA3 05F2 A7A0 40A5 34E5 AA0B"; id="0x34E5AA0B"; get= User-Agent: Evolution 3.48.1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=-l/Qmd6PDtTIm32zpIoyp Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable On Sun, 2023-05-21 at 07:56 -0700, Mike Lissner wrote: > > As far as I know it's impossible to reliably pg_upgrade a node > > that has subscriptions and eventually resume logical > > replication.=A0 > >=20 >=20 >=20 > Should this go in the documentation somewhere? Maybe in the > pg_upgrade notes? I still don't understand the mechanism. You also > say that: > =A0 > > It's possible to make it work with some efforts in some basic > > configurations and / or if no changes happen on the publications > >=20 >=20 >=20 > But that kind of surprises me too, actually, because it seemed like > pg_upgrade wiped out the LSN locations of the subcriber, making it > start all over. >=20 > Upgrading a subscriber seems like something that could/should work, > so it should be documented if pg_upgrade is incompatible with > maintaining a subscription, shouldn't it?=20 The docs are strangely silent on this. AFAIK pg_upgrade on either the publisher or subscriber breaks logical replication, which does make sense since pg_upgrade basically makes a new database cluster as it runs. There is a way to manually set the LSN position of an enabled=3Dfalse replication slot, but I've failed to make that work right in tests so far. --=-l/Qmd6PDtTIm32zpIoyp Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
On Sun, 2023-05-21 at 07:56 -0700, Mike Lissner w= rote:
=
As far as I know it's impossible to reliably pg_upgrade a= node that has subscriptions and eventually resume logical replication.&nbs= p;


Should this go in the do= cumentation somewhere? Maybe in the pg_upgrade notes? I still don't underst= and the mechanism. You also say that:
 
It's possible to make it work with some efforts in some basic configuratio= ns and / or if no changes happen on the publications


But that kind of surprises me too, actually, beca= use it seemed like pg_upgrade wiped out the LSN locations of the subcriber,= making it start all over.

Upgrading a subscriber = seems like something that could/should work, so it should be documented if = pg_upgrade is incompatible with maintaining a subscription, shouldn't it? <= br>

The docs are strangel= y silent on this. AFAIK pg_upgrade on either the publisher or subscriber br= eaks logical replication, which does make sense since pg_upgrade basically = makes a new database cluster as it runs.

There is = a way to manually set the LSN position of an enabled=3Dfalse replication sl= ot, but I've failed to make that work right in tests so far.
--=-l/Qmd6PDtTIm32zpIoyp--