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 1jMaK5-0008W6-A4 for pgsql-bugs@arkaria.postgresql.org; Thu, 09 Apr 2020 16:46:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jMaK3-0008Iz-9Z for pgsql-bugs@arkaria.postgresql.org; Thu, 09 Apr 2020 16:46:35 +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 1jMaK2-0008Ir-NG for pgsql-bugs@lists.postgresql.org; Thu, 09 Apr 2020 16:46:35 +0000 Received: from mail.dalibo.com ([212.85.157.172]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jMaJx-0006dA-V6 for pgsql-bugs@lists.postgresql.org; Thu, 09 Apr 2020 16:46:32 +0000 Received: from firost (larco.ioguix.net [82.66.0.6]) by mail.dalibo.com (Postfix) with ESMTPSA id AD3BC1FB2F; Thu, 9 Apr 2020 18:46:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1586450785; bh=k0o9LiLsYFagjqcXH/MMxW4dgczbBeD1c2a2B9VHWZk=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=CZHSEiNP06DzsLU806w2ejBtFVh1VD55i7BfbjCADRFkekbPyTqyCK1Ieh+lFjBaJ rN8p55XRA0leIUbK9JUX24+tPG6ifYEClPRpbOcGG2ztL66ypqbnC+WDZhS7t+E2dV tfML7arpfoGFXMxjUtpDK2bu0aGOpSAxn7xxWL5k= Date: Thu, 9 Apr 2020 18:46:22 +0200 From: Jehan-Guillaume de Rorthais To: Michael Paquier Cc: Fujii Masao , Kyotaro Horiguchi , pgsql-bugs@lists.postgresql.org Subject: Re: [BUG] non archived WAL removed during production crash recovery Message-ID: <20200409184622.390f9b7f@firost> In-Reply-To: <20200408135830.25a8e2ef@firost> References: <20200402.130443.1791362864704140391.horikyota.ntt@gmail.com> <20200402.130734.613319908534820379.horikyota.ntt@gmail.com> <03900fc5-fff4-109a-fe69-83de2c167929@oss.nttdata.com> <20200402.162323.770257425358491539.horikyota.ntt@gmail.com> <20200402154915.4984cff2@firost> <3d543ef2-ae02-5e59-3bfe-b79d00dab360@oss.nttdata.com> <20200403182625.0fccc6fd@firost> <4d48dbdb-e1db-a2d6-2fb2-c2a66efa7818@oss.nttdata.com> <20200407171736.61906608@firost> <20200408022345.GC1606@paquier.xyz> <20200408135830.25a8e2ef@firost> Organization: Dalibo MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/qQk8YZ8DQFVeW91zVoeDWR1" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --MP_/qQk8YZ8DQFVeW91zVoeDWR1 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, 8 Apr 2020 13:58:30 +0200 Jehan-Guillaume de Rorthais wrote: [...] > > May I ask why this new test is added to 011_crash_recovery.pl which is > > aimed at testing crash and redo, while we have 002_archiving.pl that > > is dedicated to archiving in a more general manner? > > I thought it was a better place because the test happen during crash recovery. > > In the meantime, while working on other tests related to $SUBJECT and the > current consensus, I was wondering if a new file would be a better place > anyway. So, 002_archiving.pl deals more with testing recovering on hot standby side than archiving. Maybe it could be renamed? While discussing this, I created a new file to add some more tests about WAL archiving and how recovery deal with them. Please, find the patch in attachment. I'll be able to move them elsewhere later, depending on the conclusions of this discussion. Regards, --MP_/qQk8YZ8DQFVeW91zVoeDWR1 Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=0002-v3-Add-tests-relative-to-WAL-archiving.patch