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 1pUKc3-0007Pr-Cd for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Feb 2023 04:50:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pUKc2-0003Xv-7S for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Feb 2023 04:50:46 +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 1pUKc1-0003Xm-Rc for pgsql-hackers@lists.postgresql.org; Tue, 21 Feb 2023 04:50:45 +0000 Received: from mail-pj1-x102c.google.com ([2607:f8b0:4864:20::102c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pUKbz-0005m4-HJ for pgsql-hackers@lists.postgresql.org; Tue, 21 Feb 2023 04:50:44 +0000 Received: by mail-pj1-x102c.google.com with SMTP id oe18-20020a17090b395200b00236a0d55d3aso3976751pjb.3 for ; Mon, 20 Feb 2023 20:50:43 -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=QXFulxnMZKW1ZR0nWQJifN+Uqds6l4VpV/8ZbS7DBZo=; b=d4kqWdZcNhJOnpOxnDVXqPaNfdIGGqRRUAYMwFOwKvaO81s/TQ4EcXwwZypDwx1ATh TbO3YDAK3T8rtp/TTEkHqFI3g/8ZYocuF5CHgXz1mAm6KPQt4k3f8T/w+uxjBqCtppZU 0PaNQMMpLKMwzSaz6rgKCppdY/a+BKUYQo+YwX89KrpYIq/y3eblV8ZEAPIZlr+WG+Kp 2BVvfxgSA6V/Z49vXPJrIkM2IOIaemHycp6gvPOhrcADW+5OIPnd7RTgOiV1zIrflC6S LTjZxFOkCS7QubVG+W3JY2i7iTFwGLuQdlTBol0QNZucFSpOKhAcOoVPcdN/qVKxe4Wy PCOQ== 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=QXFulxnMZKW1ZR0nWQJifN+Uqds6l4VpV/8ZbS7DBZo=; b=IBGgmGNKSqZPHWOPsqewAcUlA4L5WWLdScMz4KxhoyB8/QsFvn4Sug600LOTnBc1vR Aj0LcVmV1ieHGkJbT0cAx5Zry5yBE1cCKlvpDAneEwyfqAC0XfqNvlvD/scXJu5Yl7Cn hjivBH0+48qrU9bk3MTyF9xTs7Kb7aFMO1yKvZEE+VaszQW6Y6DLFwDCmLWut2YDHhQE wdJ0Fea7YWg4MRcyQWhfFU8ccxbY/aTwpnY+u7UI3xvbjEBmEsDa9dDzzbykwYXHZJFf VqM+h4kwzimfd/wA3hPJK+K5Xh9tlQtNbFF3CYoceeiYQe4rRB77DxoljX8UmJBI0hSv mNhg== X-Gm-Message-State: AO0yUKUbBVXujcmLxByMK5aFmPKOuJjaBQ+i5RfQjLb/LFpXbPlyrIgG 9mnFLP411YEA5gmjpBtpskw= X-Google-Smtp-Source: AK7set8mVTYWY2PtUHELtI24B9QQYxTR9jF8qTCBOSPWJMY4Nxg65QORp3MV0db8JzLtfcnAxYCCig== X-Received: by 2002:a17:902:d487:b0:19a:a6c4:6403 with SMTP id c7-20020a170902d48700b0019aa6c46403mr5568898plg.1.1676955043075; Mon, 20 Feb 2023 20:50:43 -0800 (PST) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id l11-20020a170902d34b00b00198e1bc9d83sm8766146plk.266.2023.02.20.20.50.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 20 Feb 2023 20:50:42 -0800 (PST) Date: Mon, 20 Feb 2023 20:50:39 -0800 From: Nathan Bossart To: Michael Paquier Cc: Andres Freund , Robert Haas , Tom Lane , Thomas Munro , Fujii Masao , Postgres hackers Subject: Re: Weird failure with latches in curculio on v15 Message-ID: <20230221045039.GA4026654@nathanxps13> References: <20230208222554.GB546776@nathanxps13> <20230209002413.GA603595@nathanxps13> <3907196.1675957889@sss.pgh.pa.us> <20230209192952.jvx56yuutlxuvjjf@awork3.anarazel.de> <20230214174755.GA1348509@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Feb 21, 2023 at 09:03:27AM +0900, Michael Paquier wrote: > On Tue, Feb 14, 2023 at 09:47:55AM -0800, Nathan Bossart wrote: >> Here is a new version of the stopgap/back-branch fix for restore_command. >> This is more or less a rebased version of v4 with an added stderr message >> as Andres suggested upthread. > > So, this thread has moved around many subjects, still we did not get > to the core of the issue which is what we should try to do to avoid > sporadic failures like what the top of the thread is mentioning. > > Perhaps beginning a new thread with a patch and a summary would be > better at this stage? Another thing I am wondering is if it could be > possible to test that rather reliably. I have been playing with a few > scenarios like holding the system() call for a bit with hardcoded > sleep()s, without much success. I'll try harder on that part.. It's > been mentioned as well that we could just move away from system() in > the long-term. I'm happy to create a new thread if needed, but I can't tell if there is any interest in this stopgap/back-branch fix. Perhaps we should just jump straight to the long-term fix that Thomas is looking into. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com