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 1mF1Up-0003e4-15 for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Aug 2021 21:47:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mF1Um-0000D0-MA for pgsql-hackers@arkaria.postgresql.org; Sat, 14 Aug 2021 21:47:12 +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 1mF1Um-0000Cp-5y for pgsql-hackers@lists.postgresql.org; Sat, 14 Aug 2021 21:47:12 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mF1Uf-0000FA-65 for pgsql-hackers@postgresql.org; Sat, 14 Aug 2021 21:47:10 +0000 Received: by mail-io1-xd34.google.com with SMTP id a13so17944709iol.5 for ; Sat, 14 Aug 2021 14:47:04 -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=VbUToVkOKS8LJsRaldHJXAxYrWDpCLCtVEtqUZcGvJA=; b=YRTIQAzHMxESF+BcKkBevu0lxHeHbnnMxH0v6Sv25b6zvDlwRddnPuhpEIgDpF9vdW 9IswILW2aI2VDudRKGtTkOqmwCB4p1iSGiVulFhxp53jcyo6frac/wsiL7W5qTNHFb+8 j3097S7MDsEf1apsk+43NhNKM0EhXWMwjU4awvDBGjGgsntLjYBJQy91aRB503Gw/3EM NH4Oz/sJEtgOI3mYwxYklZw9wv4vtxSlLozRg8HHiYjo44aNmwsdZ4SCaDhpgU4j7cqg ybraXsLgRtBkz2tkOa4feY3+D8eOUlfoDFRtEiYmSEDmJNBwXmNh9EYw9DnO1qiJQWPV s3rA== 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=VbUToVkOKS8LJsRaldHJXAxYrWDpCLCtVEtqUZcGvJA=; b=H7bYFFBxX+Y9/GpXijjR+S+8cKu/tNENx5lPnrt+uBBokIHsonHkEcFfqINpvBBxDt zA3Z7PlqqC1Kao+zf0/3FBXhjDfWAOQtAVTNjaWtJecdOeT5hU9vU0QbpfmA1BM+D+H0 pTTZ2TFemQSFfgdsv3klaJyM43HIvuturirYNCr44cu+SB2sis/kP1QBJvCx3Aykf1ry iVHCuG3QHJAtIUrCif6xLLoN2aMRM/mHxJ7QHOmq4SyJCYh+PGNy34kKyOfcWA28CDK8 Z9OjkQ5yBDKnTwr+RY2o2P+aVpL7ByiuUXqTDotbZv77eWOB5VKsH2UYa9GpPSObYyL2 Mwmg== X-Gm-Message-State: AOAM531/R+tw94NJBcMsExUjRzYmZ3cPSnd2x3dWEZ/bpMgylNn71wbc BOWhGIuSPANgNstqbdK/HHrQNA== X-Google-Smtp-Source: ABdhPJwSVxsqNSCXdlFSi25NHj/4BnPMJZ+Q94xb7Oz7heAkIfnUGsVshrTkEK11nc2BK7NtV+eSHw== X-Received: by 2002:a5d:8611:: with SMTP id f17mr7171909iol.153.1628977623693; Sat, 14 Aug 2021 14:47:03 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id a6sm2923902ilb.59.2021.08.14.14.47.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Aug 2021 14:47:02 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 720C98008E0; Sat, 14 Aug 2021 16:47:00 -0500 (CDT) Date: Sat, 14 Aug 2021 16:47:00 -0500 From: Justin Pryzby To: Robert Haas Cc: Nitin Jadhav , 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: <20210814214700.GO10479@telsasoft.com> References: <20210617125254.GB31772@telsasoft.com> <20210721131326.GA19620@telsasoft.com> <20210725175654.GA23997@telsasoft.com> <20210726153023.GC23997@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210726153023.GC23997@telsasoft.com> 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 Should this feature distinguish between crash recovery and archive recovery on a hot standby ? Otherwise the standby will display this all the time. 2021-08-14 16:13:33.139 CDT startup[11741] LOG: redo in progress, elapsed time: 124.42 s, current LSN: 0/EEE2100 If so, I think maybe you'd check !InArchiveRecovery (but until Robert finishes cleanup of xlog.c variables, I can't say that with much confidence).