Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1riiCo-001BZq-7i for pgsql-general@arkaria.postgresql.org; Fri, 08 Mar 2024 21:56:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1riiCm-00GNFJ-GU for pgsql-general@arkaria.postgresql.org; Fri, 08 Mar 2024 21:56:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1riiCk-00GNF5-Ro for pgsql-general@lists.postgresql.org; Fri, 08 Mar 2024 21:56:40 +0000 Received: from fhigh8-smtp.messagingengine.com ([103.168.172.159]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1riiCf-003W9d-1b for pgsql-general@lists.postgresql.org; Fri, 08 Mar 2024 21:56:38 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfhigh.nyi.internal (Postfix) with ESMTP id ADDC811400DE; Fri, 8 Mar 2024 16:56:30 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 08 Mar 2024 16:56:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1709934990; x=1710021390; bh=JNVulVne05uRPupYsaiwgZI0wH5vkeMu+64wtniIKKk=; b= XFxp06bgg7pSbHUgi6gDHKu9jguYwvUcXRbbCu04b6hSDT1GxZSGD9+Iusv2MlyE jTylvMFYkh1l8N44p2YzqwueT0NLfOJod9VnVKLUXCEJbK4w83jt1xFv7DhOBCfc f6R+piHYsRgUjfjVgwgdiEOEQREWP2QGty5bv9Ne4IyeInJPL7iZgj/Nibfv3CMv L7dHCUky0+nbQiXyDMVnfmIW+tXbmUKcDvFHLsToqIebLzRALwm5V/6qRgFkGztD ESyu79I/nsO6Ouh/8jG0HlKRiE1jukiGOMlX39d+pLWf+8+wlR8IhrEMs+i1d6r4 5VIBavshDX2b3oo/VcDy6A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1709934990; x= 1710021390; bh=JNVulVne05uRPupYsaiwgZI0wH5vkeMu+64wtniIKKk=; b=C KwMtyL7zdyLTG8H1JBMU9YbsGJLDXq8+aSvijlrpmYE53OMvZoR7t87GeQ7hR3Ul vjHW2rI3zRFt9Q/Z86lhTDm2Ki4MuRIEPlwJTteKRIJuoVIpZSgyK9b773VUu61r SeiPcYvrOSyRbMtyyR/MQ0dDp5tjTvp5xN2/wCynmho/jYQPKhMUKkwbQpF/uFAe DPPWXz4DhGyY1Fo4ohv6XF7ieP1EeLydyEsIzK7YHdWdEAdgavM6zlC+gDepFRjH dGL7nKNipMxV6Lne00xPdnm6UZT8qXjZCkga0yPIaW0DphG2L8RDg2U/7fzwWO0c HGfmeLB9Xe6yw/CgN6WSg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrieehgdduheefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeeivdfhieehheegueeileejieettdejhedugeefleek vdelkeehtdfgiefffeekudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 8 Mar 2024 16:56:29 -0500 (EST) Message-ID: Date: Fri, 8 Mar 2024 13:56:29 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Help diagnosing replication (copy) error Content-Language: en-US To: Steve Baldwin , "pgsql-generallists.postgresql.org" References: From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 3/8/24 13:50, Steve Baldwin wrote: > Hi, > > I'm in the process of migrating a cluster from 15.3 to 16.2. We have a > 'zero downtime' requirement so I'm using logical replication to create > the new cluster and then perform the switch in the application. > > I have a situation where all but one table have done their initial copy. > The remaining table is the largest (of course), and the replication slot > that is assigned for the copy > (pg_378075177_sync_60067_7343845372910323059) is showing as > 'active=false' if I select from pg_replication_slots on the publisher. What are the rest of the values in pg_replication_slots? Is there data in the subscriber side table? What are the publisher and subscriber configurations? > > I've checked the recent logs for both the publishing cluster and the > subscribing cluster but I can't see any replication errors. I guess I > could have missed them, but it doesn't seem like anything is being > 'retried' like I've seen in the past with replication errors. > > I've used this mechanism for zero-downtime upgrades multiple times in > the past, and have recently used it to upgrade smaller clusters from > 15.x to 16.2 without issue. > > The clusters are hosted on AWS RDS, so I have no access to the servers, > but if that's the only way to diagnose the issue, I can create a support > case. > > Does anyone have any suggestions as to where I should look for the issue? > > Thanks, > > Steve -- Adrian Klaver adrian.klaver@aklaver.com