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.96) (envelope-from ) id 1wSDhC-0032aW-1V for pgsql-bugs@arkaria.postgresql.org; Wed, 27 May 2026 12:49:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wSDh9-008HX5-0x for pgsql-bugs@arkaria.postgresql.org; Wed, 27 May 2026 12:49:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wSDh8-008HWx-2w for pgsql-bugs@lists.postgresql.org; Wed, 27 May 2026 12:49:11 +0000 Received: from forwardcorp1a.mail.yandex.net ([178.154.239.72]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wSDh5-000000010vc-3A2D for pgsql-bugs@lists.postgresql.org; Wed, 27 May 2026 12:49:10 +0000 Received: from mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:bf1f:0:640:c739:0]) by forwardcorp1a.mail.yandex.net (Yandex) with ESMTPS id 95AE2C0478; Wed, 27 May 2026 15:49:02 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:896::1:2e]) by mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net (smtpcorp) with ESMTPSA id 1nY6K20aG0U0-TSjhYySK; Wed, 27 May 2026 15:49:02 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1779886142; bh=xHhWg0bfHy2vu2mHkT80cby7hCF5F3B4mb0p4ktvSgs=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=lpIY+hoDOqxX0XrKBDH/YJCelHZIApkwv3rplkRv/CTiRh2FgGAGghFTdbOXppNdH UKrf+6KbfPJyFOyAOC+jAThhuzFWHYcyu/uoSt7BFVNCcxobdXpgHgCchNt4+R/ep+ Y/93ZDgd4VpKGsT0v4EkkQz3Oglw3pSD5Iyh7MWg= Authentication-Results: mail-nwsmtp-smtp-corp-main-66.iva.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\)) Subject: Re: 16.14 regression: startup process self-deadlocks during multixact WAL replay in RecordNewMultiXact From: Andrey Borodin In-Reply-To: Date: Wed, 27 May 2026 17:48:51 +0500 Cc: PostgreSQL mailing lists Content-Transfer-Encoding: quoted-printable Message-Id: <106926E9-B7D6-4F6A-A03C-94BFA76E9E4A@yandex-team.ru> References: To: Olegs Germanovs X-Mailer: Apple Mail (2.3864.600.51.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 27 May 2026, at 17:33, Olegs Germanovs = wrote: >=20 > After upgrading from 16.13 to 16.14, archive recovery of a basebackup > hangs indefinitely during multixact WAL replay. Hi Olegs! Thanks for the detailed report! Your analysis of the self-deadlock is = spot on. The fix for this problem has already been committed to REL_16_STABLE as = 42a3194e5483 [0]. It was discussed on the pgsql-bugs thread "BUG #19490: Streaming standby = on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8" [1]. Please let us know if you still observe the problem or any other unusual = behavior. Best regards, Andrey Borodin. [0] = https://git.postgresql.org/cgit/postgresql.git/commit/?h=3DREL_16_STABLE&i= d=3D42a3194e548349b658a808347df3d3d5e6b968af [1] = https://www.postgresql.org/message-id/flat/46FE61C9-F273-45FD-BED7-0F8CDA6= EB992%40yandex-team.ru#69de260aa4dc6a1882732d466783afc9=