Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pOMtS-0005Hh-Fj for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Feb 2023 18:04:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pOMtQ-00083m-TO for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Feb 2023 18:04:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pOMtQ-00083d-Ig for pgsql-hackers@lists.postgresql.org; Sat, 04 Feb 2023 18:04:04 +0000 Received: from mail-pl1-x630.google.com ([2607:f8b0:4864:20::630]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pOMtK-0000l9-7d for pgsql-hackers@lists.postgresql.org; Sat, 04 Feb 2023 18:04:03 +0000 Received: by mail-pl1-x630.google.com with SMTP id z1so8292837plg.6 for ; Sat, 04 Feb 2023 10:03:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=vvbxJRblZcqO5fYvt9ixliXHDzhzaPerk6sTIGt+C4g=; b=NfK5INTyxojWWID6ZA2+U26+uxbZTBguZQW0QKJE8G3ZFSDVjRRl03/ad3dhGN06pj 6J+ODLd02zRjTXk8e9o7hgTI3CBfdkpuB/y9ldq1248/082VsbD2jQB8ZSGcQu9ml8eC eACQ23TjB8MnUKPhY9wA8SGqmCKtTTLMOGagFVOFJYxGmQxGY/sXLYajq6y4JhUz8tH9 /fws7AWpEk0AuVBRLB/27vJtifY/xe/rDUS+ggSWq209oZwxU14Rs5LOBR4MZ0ZOwa7u XL7H2VHGtwVU2dBXMD14HA27LX95QyA3jYPZBPPyv1Ea5AJcEbKhh6G3Ije4Al3iG7rJ Ul0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=vvbxJRblZcqO5fYvt9ixliXHDzhzaPerk6sTIGt+C4g=; b=PcUosdmsDiUElaLeD440xTxsAL+q1DFRWadvRGMH5eGxalRfEDaJX3F5Pmou/ts2IL lJmjmBpTEbKikCRblxTMSGVaJ7wZvZVjaxufyZEo74mslOnskk785y3aE3xY5zmaAYN+ caG8XBhIhIVzNP7pdNZJAwqXkIB+Twbzrl3gj6DNnjWtYCZBcLE2DA0Ou4AvDxYx2bE2 Nm1e4RZZyZXgXRpeybcLmeIo0MrYemPm2KQKbrg/X6McQlPeQpCZaFxy1jwlfZmS0bkD jLSsl/GN2LN5N1DfJhY+C/wEwQbn9N3uo9g1C668XEioBobNVs5U0quTmelfp7wScCMU Uf+g== X-Gm-Message-State: AO0yUKVEILncTL/2wIS2b0FQ/veDsWB7Nfy98LzbvXUu5Oz3+IGK3gGj 9i7FX8QaJZdA1XN1MxiPmiM= X-Google-Smtp-Source: AK7set9scZYzcf6202EkEBgqYcfvTk+dV7kp11oStv4sIhXjnkGxbpIgarrpHJrYomAxFQd+KRnkYg== X-Received: by 2002:a17:902:e192:b0:198:dd4a:c6e4 with SMTP id y18-20020a170902e19200b00198dd4ac6e4mr5450250pla.33.1675533837195; Sat, 04 Feb 2023 10:03:57 -0800 (PST) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id 19-20020a170902ee5300b00194ae12a313sm3743320plo.222.2023.02.04.10.03.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 04 Feb 2023 10:03:56 -0800 (PST) Date: Sat, 4 Feb 2023 10:03:54 -0800 From: Nathan Bossart To: Andres Freund Cc: Michael Paquier , Tom Lane , Thomas Munro , Fujii Masao , Postgres hackers Subject: Re: Weird failure with latches in curculio on v15 Message-ID: <20230204180354.GA258107@nathanxps13> References: <20230201021206.wobi3dsnnuany3yq@alap3.anarazel.de> <20230201105514.rsjl4bnhb65giyvo@alap3.anarazel.de> <1369666.1675264346@sss.pgh.pa.us> <20230201165801.33ydbxvjdbomjqa7@alap3.anarazel.de> <20230201175806.GA3199959@nathanxps13> <20230201223555.GA3721373@nathanxps13> <20230204113029.xlcqrbxhp6lerrnc@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230204113029.xlcqrbxhp6lerrnc@alap3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Feb 04, 2023 at 03:30:29AM -0800, Andres Freund wrote: > That's kind of my problem with these changes. They try to introduce new > abstraction layers, but don't provide real abstraction, because they're > very tightly bound to the way the functions were called before the > refactoring. And none of these restrictions are actually documented. Okay. Michael, why don't we revert the shell_restore stuff for now? Once the archive modules interface changes and the fix for this SIGTERM-during-system() problem are in, I will work through this feedback and give recovery modules another try. I'm still hoping to have recovery modules ready in time for the v16 feature freeze. My intent was to improve this code by refactoring and reducing code duplication, but I seem to have missed the mark. I am sorry. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com