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 1lHmqI-0007qa-Hz for pgsql-docs@arkaria.postgresql.org; Thu, 04 Mar 2021 12:12:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lHmqH-00087a-G9 for pgsql-docs@arkaria.postgresql.org; Thu, 04 Mar 2021 12:12:33 +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 1lHmqH-00087T-4l for pgsql-docs@lists.postgresql.org; Thu, 04 Mar 2021 12:12:33 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lHmqF-0003th-6M for pgsql-docs@lists.postgresql.org; Thu, 04 Mar 2021 12:12:32 +0000 Received: by mail-ej1-x632.google.com with SMTP id ci14so29884868ejc.7 for ; Thu, 04 Mar 2021 04:12:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=n9cF6QwTi/H9jbFeVi32p2zHyMaJCwksTb2H8txYb6w=; b=HEW7FBIQZUBOiv9Lo39JI6mfGwm7I6Tycr/w39KVpvxRwBW+K0EJBIYOxAHmamL4Wo 6UWrpvgbWWvEl2/G3uNMut1BnmBVPWHAx00plIosGbncsX8BgBk8w2HuylM0cA9Qlu8p vNZMaymJ4qqii2P2A4t7dYhKCTwhCrugmPSfC7oBSupvnpc169uVg4v784r7V9Lf63oP GcClwOPdgxbjSDpnFMwcM3AmxtWUot3vg2vTFwSAl1wf7A7JkG2whlNh3M4XEQejGcic zliyzEZgk5Gx1hFGVgMLACJkqDp325yqZqzXoOrOV0QEHeAfAqy3pgH+ro5Rys6VP1ax 4SjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=n9cF6QwTi/H9jbFeVi32p2zHyMaJCwksTb2H8txYb6w=; b=TdSZsJOtxfnamXKUS7rWxHigtPcKFN2XtejtNZLwph0d/5dntBzs17+CnWFL2pKJzi Ef73unSguQ/4fc3A51V1J1AZei28RywCrZiR8ozb9B/2ZrwN8JU7W8Imfw7EedIJOtiX v3RNNtpJ5N0UvAAc7A3ADAB1PMz9A4vE0nE+yTeUJIpvVHV8VvCQs/uv26YInKmvOFE5 V84gYzHky0+g4jYgvIvnRwEypgGuwwIb3Awi0eINk2rzLEza853g96673QkYizJy5Wm/ yfGyGtcctsr09tfUA1AQAlupk58jsiz6uhPCvwieGNxR4+oxR8gT+dCORJTNEFAsTqMw XwRg== X-Gm-Message-State: AOAM531MrLjWyib9qBvjJ4JO4GB4yiiVbvWH5Os/Ej/4C+m3PTiew1Ua XQ3IbbKBUjBFFsUdevCEAX6bAg== X-Google-Smtp-Source: ABdhPJzMEbH7fiXNbg+0zp2Nh4pCOAf2xXmWvQB4CR5hxbPNX8/z/sjWpb2lynfXY1Xhuoeh4EMHvA== X-Received: by 2002:a17:906:b047:: with SMTP id bj7mr3841753ejb.335.1614859949357; Thu, 04 Mar 2021 04:12:29 -0800 (PST) Received: from localhost.localdomain (217-149-173-250.nat.highway.telekom.at. [217.149.173.250]) by smtp.gmail.com with ESMTPSA id n5sm24373557edw.7.2021.03.04.04.12.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Mar 2021 04:12:29 -0800 (PST) Message-ID: Subject: Re: Step 8 does not perform as documented From: Laurenz Albe To: sacrophyte@gmail.com, pgsql-docs@lists.postgresql.org Date: Thu, 04 Mar 2021 13:12:25 +0100 In-Reply-To: <161479068834.1050.3165670090780890036@wrigleys.postgresql.org> References: <161479068834.1050.3165670090780890036@wrigleys.postgresql.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 2021-03-03 at 16:58 +0000, PG Doc comments form wrote: > Under the steps of Recovering with continuous logging, Step 8 says: > "Start the server. The server will go into recovery mode and proceed to read > through the archived WAL files it needs. Should the recovery be terminated > because of an external error, the server can simply be restarted and it will > continue recovery. Upon completion of the recovery process, the server will > remove recovery.signal (to prevent accidentally re-entering recovery mode > later) and then commence normal database operations." > > The server went into recovery mode as expected. However, at the completion > of the recovery process, the server did *NOT* remove recovery.signal. Nor > did the server commend normal database operations. I manually shut down the > server, then removed recovery.signal and restarted the server, but then the > server recover _past_ my recovery_target_time. I am not sure why. The log messages should tell you what is going on. Perhaps you used a wrong time zone. Yours, Laurenz Albe