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 1mg1ST-00028N-5h for pgsql-admin@arkaria.postgresql.org; Thu, 28 Oct 2021 09:12:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mg1SR-0001Be-Nt for pgsql-admin@arkaria.postgresql.org; Thu, 28 Oct 2021 09:12:23 +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 1mg1SR-0001B5-BH for pgsql-admin@lists.postgresql.org; Thu, 28 Oct 2021 09:12:23 +0000 Received: from mail.unimaticaspa.it ([89.97.230.136]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mg1SL-0004m1-Kt for pgsql-admin@lists.postgresql.org; Thu, 28 Oct 2021 09:12:19 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/simple; d=unimaticaspa.it; s=mail; h=Message-Id:Content-Transfer-Encoding: Content-Type:Subject:From:To:MIME-Version:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=kSfTc7DtCL3fYHGzHTjZ1K+mr12xLyAPUNWJY1faGwA=; b=lkLCNSwOw1c10byKkkVpvmsr+U JtPF7o/2L4kyMeBAQnKZllW6PRtpkH1N5ymHFGfWtGiX6De1ccmAK+E1SRXHae4vj4iIXuIIaVkcV kenZSd7ZCvjrbdKzg5Du0alCoAPmTPK0QvqqlheaFw2w6K56eIQgO2h4X5ETouC4Syt5oNrtMCb8F aYrquYGXnN4j/aucqekA8JWLsv7BkPCDP7cCBd2EyN3770cv4Vg5PT2sY9kn78igsGC2OMrcSFhgP B1Kagr/wxSQVl7ecJ3bOyqw5eRyLpLsm4XU8FXW9F/4AzfhW183CUa/1WCMRUHTG3sJ2vm3Ivxzg+ K/zLeNdyjwZPB0NIBO+r/mz6m6nSAuFmWAePT0UFsI1w6g2PCaRwUK+adrndHHbP0Yc3ASMKT0TP7 rWNMm75kGKnCbqqXzWP5THwEFOQOAvSXXzIYlNYuZbpCPJ5HXmf4L8t2AmYGAn3rbCYrTTiccuRRr wtb3Cl4XmT2vXmaRfeRqtHQiXUdtkdvZ9wn/oiQ6eAJ8UWZfkY/nffIRaDUbUwlAJeVkk+Dhy3JJm leqBEn4dAiVai8sIt6LZhRT6uAKDCJ1qEx4LjCbqdDOzJxUtaw507QtakZTc1+Hjqwj//xt3eAWsy 7+6bvmA5+9YexJELSMKmTZbGeLSCWE5HOn8QnK8Os=; Received: from pc-ortensi.unimatica.lan ([10.143.90.16]) by mail.unimaticaspa.it with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1mg1SF-000Mdb-9e for pgsql-admin@lists.postgresql.org; Thu, 28 Oct 2021 11:12:11 +0200 Date: Thu, 28 Oct 2021 11:12:10 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 To: pgsql-admin@lists.postgresql.org From: Massimo Ortensi Subject: Activate a standby database and then revert to standby Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Unimatica-LocalUser: true Message-Id: <1mg1SF-000Mdb-9e@unimaticaspa.it> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I need to activate (open in read and write) a standby database, perform some action and then revert it to the previous status of standby and thus starting again loading wals from when it stopped. How should I proceed to be sure it's possible to get "back in time" to the standby db ? It's a huge DB and can't afford restarting sync from scratch