Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdi33-0000k9-JM for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jun 2019 21:23:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hdi32-0006VD-CX for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jun 2019 21:23:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdi31-0006Qq-S0 for pgsql-admin@lists.postgresql.org; Wed, 19 Jun 2019 21:23:16 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdi2z-0000aA-KS for pgsql-admin@lists.postgresql.org; Wed, 19 Jun 2019 21:23:14 +0000 Received: by mail-ot1-x333.google.com with SMTP id l15so517447otn.9 for ; Wed, 19 Jun 2019 14:23:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=aJAZ65GOk2RNr+m8dJR5LaD9YJKQeLam8EQBpzhsoIU=; b=f7vqFYlI343Woq2ox4Rg2t/86DdPM4u/sqvj7OQ5TCWAkPuEisvhqdluvk1pIglO0L YcrZZr/bQHgC16rbBUglM8Cfp5gof70cmkoGl1EfKWzaQhXpDljtS6eWnASDbUWadEAw m7KSMkza96shP5jVkpK6GU0orst30CR79anujVnFGhj5YsXHaY9nIiQ7ntFJbJqJYiNW tIZmgAs44j0M8u8YoGUdAq3RoK4dImECP3udl6MPb7IZvNfp3LyboMbjl6+ZEqslEob/ RXn0qWThpKWAgXH6Mr2is6KoofijCMioUsjrnY1z+9wv+wXWSf6X54xDRAjabLQnGfDj Go2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=aJAZ65GOk2RNr+m8dJR5LaD9YJKQeLam8EQBpzhsoIU=; b=t/Ba90kF3ZET0RjuAJueFm+vydydfuwXr8BKxrMGsoE4hkOybLPTFOHsEoXf+8rDTA wk3dIDrL73+7qHrT+13Dv6hgVVa1DNer+xLHCegBnddj6JjJedtW9g73DuGgGoFzY6SW 4zwBm4tJCDQsz/0tbHDa6G5NJcqKDACY8aKoiyiNqWG3hT1ckfkuXNmjzitS5NToCqB9 hp5OIzahclEGvTyNqaz7guWS7TgpHtFnC3LgnA/pDdzGpGRPEi5hRfsIUfoAvTsqyZJ7 yPP7pDmerHBt53rjrF7t6c2zIZzaVcSuE3otEZOzprKVcINAxbHdaozGWP6kxnWK/08P nvbQ== X-Gm-Message-State: APjAAAV0ZcOBG9XFVq3KcenRGD+iVNycp70wMMnhD7DeREObbkWpP4JK //eaz61SfW6x72FokMwex6M9WcpApCU= X-Google-Smtp-Source: APXvYqxBZ80wTaHYkCG3KqdXuj2hBCgatNix4um2bUIAsl83XIfe0t2q5ETA+swIu6FQwQCMV8zpvw== X-Received: by 2002:a9d:7b43:: with SMTP id f3mr52878711oto.337.1560979392443; Wed, 19 Jun 2019 14:23:12 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id t6sm7209563otk.36.2019.06.19.14.23.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Jun 2019 14:23:11 -0700 (PDT) Subject: Re: zero data loss recovery is possbile with pgbackrest tool? To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: Date: Wed, 19 Jun 2019 16:23:11 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 6/19/19 4:14 PM, Pavan Kumar wrote: > Hello experts, > > pgbackrest tool is possible to perform zero data loss recovery? > I did couple of test case where I have end up with data loss (data exist > in current wal). > > please share your experience/suggestion to perform complete recovery  with > this tool Set the checkpoint timeout to something closer to what you want. -- Angular momentum makes the world go 'round.