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 1mMLLE-0004xF-RF for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Sep 2021 02:23:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mMLLC-0005TF-JT for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Sep 2021 02:23:34 +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 1mMLLC-0005T7-6x for pgsql-hackers@lists.postgresql.org; Sat, 04 Sep 2021 02:23:34 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mMLL9-0007Gy-Ey for pgsql-hackers@postgresql.org; Sat, 04 Sep 2021 02:23:33 +0000 Received: by mail-io1-xd34.google.com with SMTP id y18so960785ioc.1 for ; Fri, 03 Sep 2021 19:23:31 -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=qKwQ4ty7WvJ/N9ptEULB2frDpkkPVo0L3G+tot3B+GE=; b=Qd7HG3QmbsFQMvta5N2rAssZpkgQRkKnIIuwbCYOHb+eXSSTw4XAN/zoyV3WO3IAzX 9yVSRKfH2Pbt52BY4+ZMLzTEl7sb6tcHiqX9smlMzMXXi2JKCKQTExgsqBG9GKWtZwjQ sEtg2aZBbXqAiDYpqpTj+elh+izr0ndp35vFrKIFxyJd1B/09KHW8nPINyT/vULbwUcI bM2JVweA5TLxhW/1RO/oo4adqT+wKhAqd2OWmgoyrwme7mu5CO6gTLneY0ISCWRhK2DK bpDUgYNSTYzmztQdOEsabjHf1Lp0as2CeHBq3oNcjE9mYo19oSEmY6dBcuKc9/UL0+Mt 7JWg== 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=qKwQ4ty7WvJ/N9ptEULB2frDpkkPVo0L3G+tot3B+GE=; b=hN2s9vzPZSi+z2/P/lxpdpwYvaq9H6HQsu474bakCnFCTF+3IKslwa6maFsj4jxYrJ l00Xw52Cez3qARPmqfizCqbaGGkDL7HL0R5Nbmjgh8PzdcW7nTtp1quCrWD/PE/cr7uB 9IAi7KUg/0TKbNS7ln0a8rbxfqIejVV4fwxnfnD6jwJaUR04NavH7P7mEKlc3E3V070i HOTWH38yKeihkAPHatT+BIK5QEvKX3Up6tS71FzFirq4n5jVc7iDFSNzqd7qx6LbHpIc ggEWlp24sCRzt3KEHRG0vAkTizPsnW/52UzNpUqTBKPnpKX3exkkQ9Xrs7g7Rd7nVpz/ F3dQ== X-Gm-Message-State: AOAM5303l1YJ6UN8ev6OHxTlJR7T0gMDDtZvRNmV6CcezJI9QJn15AQI SHC4O/yhE+qQ1LDRmu+VudKzUQ== X-Google-Smtp-Source: ABdhPJzDX+IAkJ3YdNAgpxKFY7S0DxGnd/6VeNEofytLBEqSM+RMEoQE+kfxmE9eMSGbUYa7vx2UwA== X-Received: by 2002:a05:6602:1346:: with SMTP id i6mr1476898iov.128.1630722208727; Fri, 03 Sep 2021 19:23:28 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id o15sm684205ilo.73.2021.09.03.19.23.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Sep 2021 19:23:28 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 3D30A800A39; Fri, 3 Sep 2021 21:23:27 -0500 (CDT) Date: Fri, 3 Sep 2021 21:23:27 -0500 From: Justin Pryzby To: Nitin Jadhav Cc: Robert Haas , Bharath Rupireddy , Tom Lane , Andres Freund , Stephen Frost , Magnus Hagander , Thomas Munro , pgsql-hackers@postgresql.org Subject: Re: when the startup process doesn't (logging startup delays) Message-ID: <20210904022327.GE26465@telsasoft.com> References: <20210721131326.GA19620@telsasoft.com> <20210725175654.GA23997@telsasoft.com> <20210726153023.GC23997@telsasoft.com> <20210814214700.GO10479@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 Fri, Sep 03, 2021 at 01:23:56PM +0530, Nitin Jadhav wrote: > Please find the updated patch attached. Please check CA+TgmoZtbqxaOLdpNkBcDbz=41tWALA8kpH4M=RWtPYHC7-KNg@mail.gmail.com I agree with Robert that a standby server should not continuously show timing messages for WAL replay. Some doc comments: + Sets the time interval between each progress update of the operations + performed during startup process. This produces the log message after Either say "performed by the startup process" or "performed during startup". s/the/a/ + every interval of time for the operations that take longer time. The unit ..for those operations which take longer than the specified duration. + used to specify the value is seconds. For example, if you set it to + 10s , then after every 10s there remove "after" + is a log message indicating which operation is going on and what is the say "..every 10s, a log is emitted indicating which operation is ongoing, and the elapsed time from the beginning of the operation.." + elapsed time from beginning. If the value is set to 0 , + then it logs all the available messages for such operations. -1 "..then all messages for such operations are logged." + disables the feature. The default value is set to 10s + "The default value is >10s<."