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 1wUHRH-0013Ys-3D for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Jun 2026 05:13:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wUHRF-00Ch17-24 for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Jun 2026 05:13:17 +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.96) (envelope-from ) id 1wUHRF-00Ch0z-0i for pgsql-hackers@lists.postgresql.org; Tue, 02 Jun 2026 05:13:17 +0000 Received: from forwardcorp1b.mail.yandex.net ([178.154.239.136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wUHRC-00000000nLq-2tJv for pgsql-hackers@lists.postgresql.org; Tue, 02 Jun 2026 05:13:16 +0000 Received: from mail-nwsmtp-smtp-corp-main-34.sas.yp-c.yandex.net (mail-nwsmtp-smtp-corp-main-34.sas.yp-c.yandex.net [IPv6:2a02:6b8:c24:fa2:0:640:41ee:0]) by forwardcorp1b.mail.yandex.net (Yandex) with ESMTPS id 1523880765; Tue, 02 Jun 2026 08:13:13 +0300 (MSK) Received: from smtpclient.apple (unknown [2a02:6bf:8080:661::1:34]) by mail-nwsmtp-smtp-corp-main-34.sas.yp-c.yandex.net (smtpcorp) with ESMTPSA id BDX8Sb2ZgiE0-7KlCfMTa; Tue, 02 Jun 2026 08:13:12 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1780377192; bh=O6+wfV0QLFC1jofMrxr7aPgtB1JQSFq1shxXiThGwBo=; h=Message-Id:To:Date:References:Cc:In-Reply-To:From:Subject; b=H+omgKZ597fesXXssJW8jgo53Rm5xqSETdZAnqi2EUlwJIMDqE6ge4j/F7PVutXvC qXWQIKLHHIgGksyHiLIkA9W0sEFDO9sENC3H6wTkzgLFCoRWp1NpsT0bHEiLsjjAo2 nmmAcwmW5brCwYTlW8HBGi1gMv8S1KH9tUmrEfJs= Authentication-Results: mail-nwsmtp-smtp-corp-main-34.sas.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: injection_points: Switch wait/wakeup to use atomics rather than latches From: Andrey Borodin In-Reply-To: Date: Tue, 2 Jun 2026 10:13:01 +0500 Cc: Robert Haas , Postgres hackers , Heikki Linnakangas Content-Transfer-Encoding: 7bit Message-Id: References: <46821C66-E6B2-420D-BB83-E20EF36665B8@yandex-team.ru> To: Michael Paquier 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 2 Jun 2026, at 09:15, Michael Paquier wrote: > > On Mon, Jun 01, 2026 at 04:25:40PM +0500, Andrey Borodin wrote: >> The shared memory segment must be released before we attempt recovery. >> But that's exactly what I wanted anyway. Thank you! > > How do you guarantee that a wait position is reached in the case where > you don't have access to wait events to make sure that the wait point > is reached? In a research test? sleep(1) Best regards, Andrey Borodin.