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 1lUxsJ-0003Gt-P9 for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Apr 2021 20:37:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lUxsH-0000NT-M4 for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Apr 2021 20:37:05 +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 1lUxsH-0000KH-BG for pgsql-hackers@lists.postgresql.org; Fri, 09 Apr 2021 20:37:05 +0000 Received: from mail-io1-xd2c.google.com ([2607:f8b0:4864:20::d2c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lUxsD-0003Pd-9V for pgsql-hackers@postgresql.org; Fri, 09 Apr 2021 20:37:04 +0000 Received: by mail-io1-xd2c.google.com with SMTP id v123so382872ioe.10 for ; Fri, 09 Apr 2021 13:37:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ECt+CBkXKnULr5hNP/fFqRXdsFtLtV63Cqty2/lvvNU=; b=fsQBIzVRDFVAZJAT0Ud2uKnDEvcnF9Ono41W7tvrwsUoirSZYk21RZxBMLeSlH3Prp 2j/nvNE4KUT19ZXqPcJpUSg1RSinpeUyu+dzhxXiCzKtCAjRijSHN8uqO9KCY+DkJExV zid1PIyh4GdQIcWXddbCN6ZWoRbNjogj8WwzSmma5lVxKm5xFy478q4ZJlNRXmZjnOEn t1lfie/9nRKRZ7HPYJ/5X930G7mm1zk0QKvTQY8dGrUEWkdLgYQtS/IvROQxPwf89/Wp eVIQNfqloJIYa1qVndwnoyZa93ZlikCYpmziX239jVLqfpVyoECC1TKnUpKN8lryID0b GgWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ECt+CBkXKnULr5hNP/fFqRXdsFtLtV63Cqty2/lvvNU=; b=epMhPaqHBgpntz21kDmmhxbbuiK8BA4FpFla1lgAgjeChIUttYMiXsxBdMaJIcTHfi M7sK71CbB9cvXbX+hNb4ampO+JdVeBqSaZiPSVgELpH1CJYfaNfkGWCSK2SXyDophqPY Sm4bi3SFhrmbUrYWQ7zh3FEb3UERuOpTE+PwVBeBncnzjICIGL0AdOTPLUXn4Y+NTwtm TK1lsa4IG6ZPaRZLsjSR1vT3qVuEpi4FHGzbfHCYFuwibk478ON0DW523nBAyKzl+AhJ mj1F6v1l6TFZBE4nqRS2S8HNMBgn0BKJb1PTtkbrZVTyYE+azxBrcrbXP/+n9HFhabPS SHnQ== X-Gm-Message-State: AOAM532yJ9rIOysp2RX5wcOjcjiEisA7V3F2Uq6k2tbVSvVP20NWmThh aN69GkLZow/bTKpx+hYsR+jNeQ== X-Google-Smtp-Source: ABdhPJzkQSt55xShrui0a4/Quz77BI9KjMgYg2gt+/DDnKQBMgTvBg6cBSvBprleSv2bfah3txt5Qg== X-Received: by 2002:a05:6602:80d:: with SMTP id z13mr12608025iow.17.1618000620163; Fri, 09 Apr 2021 13:37:00 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id k4sm1708211iol.18.2021.04.09.13.36.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Apr 2021 13:36:59 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 7639E802183; Fri, 9 Apr 2021 15:36:58 -0500 (CDT) Date: Fri, 9 Apr 2021 15:36:58 -0500 From: Justin Pryzby To: Thomas Munro Cc: Tomas Vondra , Stephen Frost , Andres Freund , Jakub Wartak , Alvaro Herrera , Tomas Vondra , Dmitry Dolgov <9erthalion6@gmail.com>, David Steele , pgsql-hackers@postgresql.org Subject: Re: WIP: WAL prefetch (another approach) Message-ID: <20210409203658.GU6592@telsasoft.com> References: <20210214231815.GO27507@tamriel.snowman.net> <17b3f450-048c-f3a6-7086-259523f33cbc@enterprisedb.com> <20210317214331.GF20766@tamriel.snowman.net> <28c3352e-5388-6410-aae7-05907079e6c9@enterprisedb.com> <8dd2dcc2-0b6b-a4ab-c1b3-032c0a5ab1c3@enterprisedb.com> <20210409033703.GP6592@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Apr 10, 2021 at 08:27:42AM +1200, Thomas Munro wrote: > On Fri, Apr 9, 2021 at 3:37 PM Justin Pryzby wrote: > > Here's some little language fixes. > > Thanks! Done. I rewrote the gibberish comment that made you say > "XXX: what?". Pushed. > > > BTW, before beginning "recovery", PG syncs all the data dirs. > > This can be slow, and it seems like the slowness is frequently due to file > > metadata. For example, that's an obvious consequence of an OS crash, after > > which the page cache is empty. I've made a habit of running find /zfs -ls |wc > > to pre-warm it, which can take a little bit, but then the recovery process > > starts moments later. I don't have any timing measurements, but I expect that > > starting to stat() all data files as soon as possible would be a win. > > Did you see commit 61752afb, "Provide > recovery_init_sync_method=syncfs"? Actually I believe it's safe to > skip that phase completely and do a tiny bit more work during > recovery, which I'd like to work on for v15[1]. Yes, I have it in my list for v14 deployment. Thanks for that. Did you see this? https://www.postgresql.org/message-id/GV0P278MB0483490FEAC879DCA5ED583DD2739%40GV0P278MB0483.CHEP278.PROD.OUTLOOK.COM I meant to mail you so you could include it in the same commit, but forgot until now. -- Justin