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 1pXE5s-0006SR-4D for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Mar 2023 04:29:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pXE5q-00050A-Id for pgsql-hackers@arkaria.postgresql.org; Wed, 01 Mar 2023 04:29:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pXE5q-000501-7W for pgsql-hackers@lists.postgresql.org; Wed, 01 Mar 2023 04:29:30 +0000 Received: from mail-pj1-x1029.google.com ([2607:f8b0:4864:20::1029]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pXE5j-0007R7-My for pgsql-hackers@lists.postgresql.org; Wed, 01 Mar 2023 04:29:29 +0000 Received: by mail-pj1-x1029.google.com with SMTP id x34so12125185pjj.0 for ; Tue, 28 Feb 2023 20:29:23 -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=CxBNyOw3JiYVHRls4bCTxcvltBk637kA9v57+m/dRs4=; b=VyVn//zV5G0rZbKgVORpwbMhDsng3N3eQGS4Kd/k+4ygTFYHY+8ZDaade45z+idVK6 is+we0xjNrkKk0As0xks5kB931nzmGhqhXnTvNjYwQfWLL5prbfI0KY9s8MhLCFvXgpQ 7fDG5MUCmobpLWiIrq3CwE605TQ3AIj7GC2ZzundMDuU0RSUulSWaapNjfksFLlk35xP H8uHjW3NbXrQ037TERxHMxQ47N0YdJE6JJsAUoTy9mlXyzhirPOY+eqA6uG4Uqc+kw2U DpnsJixZ+Yk9prBHIN4cYo9n0jcHsb6H7T59GK+W/PTT8F7he7rOsGCLlOoC0ls0V7cs gP1g== 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=CxBNyOw3JiYVHRls4bCTxcvltBk637kA9v57+m/dRs4=; b=hHua6hV8cDbKG6bye4g8YsW6ejKFjxPoJqf6GuBYqWdkO/oNHN5PGU516ej2BThbWi fTrfFjjD+px5sbH/ssVfv/D5ItZERJMtgUAV16Njw8aXaU0gXIA9TkeLHnVkUmv+17y/ 7gZ1pgzp4w4IqlcZaGgHJgFD2OC9PEXsp3EFRcInQMHlDhlMUpZx5h9mMxaQ/0uehQsx DE+PZyBuL74fHK1wr/habt1pZB4V92fyIgwF1FnSJWGNAtfZpDcY1i1Bm9+rnveeunmm +ObfRgQscBDp1KTw2eS+7oS0YKwOIXY0t/78emqsPCS40diAD6yh/xlJ90/NboRcM3ok hiwg== X-Gm-Message-State: AO0yUKXYzqWBvZWwPyA0tkGynBpkpLNWnqHCHwj+A4sdHxLji/rTmmDF 3VwfvXIMPKnkmpkR99cHOTA= X-Google-Smtp-Source: AK7set+OhM1hr/qbuj7xX4Kme7l5wgktbx5DRDCd1szyazIvwdZdGPCBX9RBAwXVgBMamtj4UjEYJA== X-Received: by 2002:a05:6a20:12d1:b0:bf:58d1:ce95 with SMTP id v17-20020a056a2012d100b000bf58d1ce95mr15435488pzg.20.1677644961932; Tue, 28 Feb 2023 20:29:21 -0800 (PST) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id q2-20020a656842000000b005026c125d47sm6568224pgt.21.2023.02.28.20.29.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 28 Feb 2023 20:29:21 -0800 (PST) Date: Tue, 28 Feb 2023 20:29:19 -0800 From: Nathan Bossart To: Andres Freund Cc: Robert Haas , Tom Lane , Michael Paquier , Thomas Munro , Fujii Masao , Postgres hackers Subject: Re: Weird failure with latches in curculio on v15 Message-ID: <20230301042919.GC1453450@nathanxps13> References: <3907196.1675957889@sss.pgh.pa.us> <20230209192952.jvx56yuutlxuvjjf@awork3.anarazel.de> <20230216163254.nktnbbb2b7wlpzwy@awork3.anarazel.de> <20230218211522.grbzg75vzjtqafzf@awork3.anarazel.de> <20230225190031.e3vesk22q5wpmmhc@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230225190031.e3vesk22q5wpmmhc@awork3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Feb 25, 2023 at 11:00:31AM -0800, Andres Freund wrote: > TBH, I think the current archive and restore module APIs aren't useful. I > think it was a mistake to add archive modules without having demonstrated that > one can do something useful with them that the restore_command didn't already > do. If anything, archive modules have made it harder to improve archiving > performance via concurrency. I must respectfully disagree that this work is useless. Besides the performance and security benefits of not shelling out for every WAL file, I've found it very useful to be able to use the standard module framework to develop archive modules. It's relatively easy to make use of GUCs, background workers, compression, etc. Of course, there is room for improvement in areas like concurrency support as you rightly point out, but I don't think that makes the current state worthless. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com