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 1r3jYv-005T6f-H8 for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Nov 2023 21:06:09 +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 1r3jYD-009KwW-RQ for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Nov 2023 21:05:25 +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.94.2) (envelope-from ) id 1r3jYD-009KwO-FX for pgsql-hackers@lists.postgresql.org; Thu, 16 Nov 2023 21:05:25 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r3jYA-005unh-Lv for pgsql-hackers@lists.postgresql.org; Thu, 16 Nov 2023 21:05:24 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 2D5182FC1417 for ; Thu, 16 Nov 2023 22:05:20 +0100 (CET) Received: from s934.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 1DBA82E279F7; Thu, 16 Nov 2023 22:05:20 +0100 (CET) Received: from s898.loopia.se (unknown [172.22.191.6]) by s934.loopia.se (Postfix) with ESMTP id 1AEBF7CEA4E; Thu, 16 Nov 2023 22:05:20 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled Received: from s981.loopia.se ([172.22.191.5]) by s898.loopia.se (s898.loopia.se [172.22.190.17]) (amavisd-new, port 10024) with LMTP id Ah6RGUXyIoQt; Thu, 16 Nov 2023 22:05:19 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s981.loopia.se (Postfix) with ESMTPSA id 8DAF622B1713; Thu, 16 Nov 2023 22:05:19 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Issue with cancel_before_shmem_exit while searching to remove a particular registered exit callbacks From: Daniel Gustafsson In-Reply-To: Date: Thu, 16 Nov 2023 22:05:19 +0100 Cc: Andres Freund , Tom Lane , Bharath Rupireddy , PostgreSQL Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <4EF5DD92-15E2-413F-AD6D-C2D29C98D29D@yesql.se> References: <1519052.1594129481@sss.pgh.pa.us> <20200707165445.6qniqhzydlfsplvw@alap3.anarazel.de> To: Robert Haas X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 30 Jul 2020, at 14:11, Robert Haas wrote: >=20 > On Mon, Jul 20, 2020 at 3:47 PM Robert Haas = wrote: >> But I also agree that what pg_start_backup() was doing before v13 was >> wrong; that's why I committed >> 303640199d0436c5e7acdf50b837a027b5726594. The only reason I didn't >> back-patch it is because the consequences are so minor I didn't think >> it was worth worrying about. We could, though. I'd be somewhat >> inclined to both do that and also change LLVM to use on_proc_exit() = in >> master, but I don't feel super-strongly about it. >=20 > Unless somebody complains pretty soon, I'm going to go ahead and do > what is described above. When backpatching 9dce22033d5d I ran into this in v13 and below, since = it needs llvm_shutdown to happen via on_proc_exit in order for all = llvm_release_context calls to have finished. Unless anyone objects I will backpatch = bab150045bd97 to v12 and v13 as part of my backpatch. -- Daniel Gustafsson