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 1t6SiG-00D99E-9i for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Oct 2024 10:47:36 +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 1t6SiE-000983-Jz for pgsql-hackers@arkaria.postgresql.org; Thu, 31 Oct 2024 10:47:34 +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 1t6Shd-00048K-5q for pgsql-hackers@lists.postgresql.org; Thu, 31 Oct 2024 10:46:57 +0000 Received: from forwardcorp1d.mail.yandex.net ([2a02:6b8:c41:1300:1:45:d181:df01]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6Sha-003yyJ-Tq for pgsql-hackers@postgresql.org; Thu, 31 Oct 2024 10:46:56 +0000 Received: from mail-nwsmtp-smtp-corp-main-56.klg.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-56.klg.yp-c.yandex.net [IPv6:2a02:6b8:c42:b1cb:0:640:2a1e:0]) by forwardcorp1d.mail.yandex.net (Yandex) with ESMTPS id CDFD460AD2; Thu, 31 Oct 2024 13:46:52 +0300 (MSK) Received: from smtpclient.apple (10.211.107.18-vpn.dhcp.yndx.net [10.211.107.18]) by mail-nwsmtp-smtp-corp-main-56.klg.yp-c.yandex.net (smtpcorp/Yandex) with ESMTPSA id lkYdCm1IWmI0-xw9DX8EH; Thu, 31 Oct 2024 13:46:52 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1730371612; bh=XgSU9fXcT3gmdwpSjrQx253c4HEpew37wx3ESAOsgeU=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=gbM4mOCg7HUHu8tm1ldBoMngsGznD9f5DZHgRiYOCJkTdjN2i2JRXX3VVOaN79Y0J 1Ob/Hc96rikRYsNA1sfRfWzGegdwY9dCO5xMPkij1tbpy5iphZrMcyPNsVT3RVtK3y bzTsao2cCpe8/MEViGzezTpBmAQxWHgPV/c+9aVE= Authentication-Results: mail-nwsmtp-smtp-corp-main-56.klg.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 \(3776.700.51\)) Subject: Re: MultiXact\SLRU buffers configuration From: "Andrey M. Borodin" In-Reply-To: Date: Thu, 31 Oct 2024 14:46:37 +0400 Cc: Michael Paquier , Alvaro Herrera , vignesh C , Andrew Borodin , Yura Sokolov , Andres Freund , Thomas Munro , Gilles Darold , Alexander Korotkov , Daniel Gustafsson , Kyotaro Horiguchi , pgsql-hackers mailing list Content-Transfer-Encoding: quoted-printable Message-Id: References: <202408221436.o6girevg72sx@alvherre.pgsql> To: Thom Brown X-Mailer: Apple Mail (2.3776.700.51) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 29 Oct 2024, at 21:45, Thom Brown wrote: >=20 > It clearly checks for interrupts, but when I saw this issue happen, it > wasn't interruptible. Perhaps, that was different multixacts? When I was observing this pathology on Standby, it was a stream of = different reads encountering different multis. Either way startup can cancel locking process on it's own. Or is it the = case that cancel was not enough, did you actually need termination, not = cancel? Thanks! Best regards, Andrey Borodin.=