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 1kkwcI-0005rT-5Z for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Dec 2020 21:58:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kkwcG-00014r-NC for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Dec 2020 21:58:20 +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 1kkwcG-00014k-HC for pgsql-hackers@lists.postgresql.org; Thu, 03 Dec 2020 21:58:20 +0000 Received: from mail-il1-x12a.google.com ([2607:f8b0:4864:20::12a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kkwc9-0002kO-JI for pgsql-hackers@postgresql.org; Thu, 03 Dec 2020 21:58:19 +0000 Received: by mail-il1-x12a.google.com with SMTP id b8so3354688ila.13 for ; Thu, 03 Dec 2020 13:58:13 -0800 (PST) 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=Sdy+kD5Nat7XsnwjXoj7owBRA1hmAD5zr/RbrfYvYHI=; b=iJqbRltIx5cPcUPX1XPzm4m5maSfHuEHfPrna8Gm7yGECOER+uXg0bOYQpYwEs5iY+ czj/v/BI2TKA45/+VyWU+IZbISQzylv58G/7YhAkUG8Tme8RPa5rk2/PVxz94iuRlLUG RSKlpQZBA7iCnJwRHXsgpB030WfW7qd5DNPNOi8HAW20jzUQUsZGOPKWsMxozJlAM5Cc Q3D/r3KDPmZMWTYrmEHlCMlu0OOGv1IDe3RhCyVVg7/vhxOwgdzl3k25NR8tezQT9HX0 YWu8p9SCXvQW4dBeP0PSOHUK3MBmciADHhzeswFLeH+e/csjsgX5lfftwFPboa1hbvke J+1Q== 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=Sdy+kD5Nat7XsnwjXoj7owBRA1hmAD5zr/RbrfYvYHI=; b=JZaBXD6nLYecp26bvcTYpIa9k4ffQOVm6wnYQceYrjP0CTRcFBIwHv3intIwINVW+G nXwU2ptGZa1byablJrcZH9zYpHUj3WlBQI57+4CEV5+E5mIDJezovRhK6Q/B1gWFSidQ DQYIpvfb2EJs/XwzHE1aHmHsCQJ4zMgehNyquUYfoYp9MhHHnx1hSOH/mb7dv09V2zW/ nxu+NUk1CoEp7lu69babmbb2G4638UAYqBABx0lGMfkbc+9ftIhePLLlS+ZwFuUgt7tI 9LkL0Lhbx9kJJs4fjCyd8Et5nc4r3vKDMx4eSMAIm473e/EIXkgalNAOtsFGMZ/6X71r DtSQ== X-Gm-Message-State: AOAM531o9oHmfabXHt80v4TOSi0y2RRF5EfUWhB7VuRbMexwHTZp4CMM WKW8Qvtsxrl0/hx2IhV8NOi1xA== X-Google-Smtp-Source: ABdhPJxImhk0mU0dAGLJ8dsSBg28qEFX/s2CBLvxBfdPvFYxKT+RgP6nKQ2n9OMx0ulYbtm9WcOhug== X-Received: by 2002:a92:5e08:: with SMTP id s8mr1661502ilb.308.1607032691879; Thu, 03 Dec 2020 13:58:11 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id g2sm328465ilh.41.2020.12.03.13.58.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Dec 2020 13:58:11 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 01BB58006C6; Thu, 3 Dec 2020 15:58:09 -0600 (CST) Date: Thu, 3 Dec 2020 15:58:09 -0600 From: Justin Pryzby To: "Bossart, Nathan" Cc: Michael Paquier , "k.jamison@fujitsu.com" , Thomas Munro , pgsql-hackers@postgresql.org Subject: Re: please update ps display for recovery checkpoint Message-ID: <20201203215809.GS24052@telsasoft.com> References: <20200818225238.GP17022@telsasoft.com> <20200820080905.GA10353@paquier.xyz> <20200831065244.GB6555@paquier.xyz> <20200910020050.GB18552@telsasoft.com> <20200910043710.GD2743@paquier.xyz> <20200919160031.GC30557@telsasoft.com> <20201002072814.GE1464@paquier.xyz> <20201002091354.GH8476@telsasoft.com> <9A1B9D98-4576-438A-943F-0AFB05946C7C@amazon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9A1B9D98-4576-438A-943F-0AFB05946C7C@amazon.com> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Dec 03, 2020 at 09:18:07PM +0000, Bossart, Nathan wrote: > I considered also checking that update_process_title was enabled, but > I figured that these ps display updates should happen sparsely enough > that it wouldn't make much of an impact. Since bf68b79e5, update_ps_display is responsible for checking update_process_title. Its other, remaining uses are apparently just acting as minor optimizations to guard against useless snprintf's. See also https://www.postgresql.org/message-id/flat/1288021.1600178478%40sss.pgh.pa.us in which (I just saw) Tom wrote: > Seems like a good argument, but you'd have to be careful about the > final state when you stop overriding update_process_title --- it can't > be left looking like it's still-in-progress on some random WAL file. I think that's a live problem, not just a concern for that patch. It was exactly my complaint leading to this thread: > But runs a checkpoint, which can take a long time, while the "ps" display still > says "recovering NNNNNNNN". -- Justin