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 1nP45p-00072P-4W for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Mar 2022 15:07:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nP45n-00015l-D0 for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Mar 2022 15:07:11 +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 1nP45n-00014r-2D for pgsql-hackers@lists.postgresql.org; Tue, 01 Mar 2022 15:07:11 +0000 Received: from mail-pl1-x62d.google.com ([2607:f8b0:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nP45k-00006Y-9C for pgsql-hackers@lists.postgresql.org; Tue, 01 Mar 2022 15:07:10 +0000 Received: by mail-pl1-x62d.google.com with SMTP id z11so5260713pla.7 for ; Tue, 01 Mar 2022 07:07:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=ntfEVPGEugObhfn2gHL63e0Cf9qGtEmV8S3pxojuUcc=; b=HINwr/0p2qxhblzoZn9ayQe10Py16zospFQ1mpUZ24QuvtVi2Ty2ERc7HSab4MCJlC XvxOzP1t6z678y+W0w/dsH7T2q3mqntclmWnGb8Y1euH1rlyVgj/nCJJ53A5qvUyXPBN 5tohLTyT2/OdCKp2UjnLKcYg8K/fU4n4I+3+tXGVfU3cQ4Sv482mbMGP4HXh/6OzeWhb RfFnoFVtGq3TQpnH/63qwskbC4uz4UkNncGK9rgrm3AVAvLotjy0obItEJV2zl/mlWxT eNQeIxzxNtc2uIYZ39kJ2+MCISjV13uHTzKGCFc4+G0VMaUzMp3fRO8oTmAvA56U3bzr y94w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ntfEVPGEugObhfn2gHL63e0Cf9qGtEmV8S3pxojuUcc=; b=PhPI19A63YH+NHWxytreNa3UR46ONXyJ6xDUDpaRm3VfHuKYfyKhS9R3Vw/BIKX8ta EL5Ri1Nih4aBO5oZfhsGOWG2rc9KI20wq5xjyJkMoo78b7BITN/uOc7ra5bmdlSjHz2j z1Fl8/7MM5fLLveTePtA0ZTk2xAufw0wrvoWrUH0FWsMhrl36tfZBmuYth7rD6t5Blih wVuWMVtuPJFWDD1QFEq+Z17ZapDWrbiS0V4LfmH7OPSV9uv4BbjciCOVqRxyDY98/LdD cSC0FN04jWmg9rGku8Z64OzPtLcioalDmiQt0SaoNJdT7WzgGzOrykRmXk8kmGLJe9qc UMTQ== X-Gm-Message-State: AOAM530t/s5+9wNlU1ItvGTloSYJF5rmhrMHdxzYj9VW07ZhrOv3ObU6 5JCPUigJhCeU+82JRvrwVvY= X-Google-Smtp-Source: ABdhPJwWGrl+IFYcHXQ8pw3Dosz2AgilQFbqzpoQbuyjTMuvw2smk7xPq7vE3dOwjaM9VGnVkro2WA== X-Received: by 2002:a17:902:e5c3:b0:14f:a4ff:34b8 with SMTP id u3-20020a170902e5c300b0014fa4ff34b8mr25461363plf.24.1646147226089; Tue, 01 Mar 2022 07:07:06 -0800 (PST) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id f18-20020a056a001ad200b004bf321765dfsm18237145pfv.95.2022.03.01.07.07.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Mar 2022 07:07:05 -0800 (PST) Date: Tue, 1 Mar 2022 07:07:04 -0800 From: Nathan Bossart To: Justin Pryzby Cc: Maxim Orlov , Pavel Borisov , "Bossart, Nathan" , Maxim Orlov , Andres Freund , pgsql-hackers@lists.postgresql.org Subject: Re: Pre-allocating WAL files Message-ID: <20220301150704.GA1030078@nathanxps13> References: <20201225200953.jjkrytlrzojbndh5@alap3.anarazel.de> <51BAAB3B-9D3C-4155-B125-42E4F06DCDF4@amazon.com> <163352276350.15435.3988688227048304232.pgcf@coridan.postgresql.org> <20220301144044.GG25269@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220301144044.GG25269@telsasoft.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Mar 01, 2022 at 08:40:44AM -0600, Justin Pryzby wrote: > FYI: this is currently failing in cfbot on linux. > > https://cirrus-ci.com/task/4934371210690560 > https://api.cirrus-ci.com/v1/artifact/task/4934371210690560/log/src/test/regress/regression.diffs > > DROP TABLESPACE regress_tblspace_renamed; > +ERROR: tablespace "regress_tblspace_renamed" is not empty I believe this is due to an existing bug. This patch set seems to influence the timing to make it more likely. I'm tracking the fix here: https://commitfest.postgresql.org/37/3544/ -- Nathan Bossart Amazon Web Services: https://aws.amazon.com