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 1jM9Ls-0002ZB-1M for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Apr 2020 11:58:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jM9Lq-0007FB-Vs for pgsql-bugs@arkaria.postgresql.org; Wed, 08 Apr 2020 11:58:38 +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 1jM9Lq-0007F4-Ir for pgsql-bugs@lists.postgresql.org; Wed, 08 Apr 2020 11:58:38 +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 1jM9Lo-0000TC-2m for pgsql-bugs@lists.postgresql.org; Wed, 08 Apr 2020 11:58:37 +0000 Received: from firost (larco.ioguix.net [82.66.0.6]) by mail.dalibo.com (Postfix) with ESMTPSA id 7E96C1FEB8; Wed, 8 Apr 2020 13:58:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dalibo.com; s=a; t=1586347111; bh=LR5TFZZWXW/eEq3/pUpx+qr5YHRz+5uIcGmM+vxNJ98=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=XsjHECQaJw1zlKQzfMcntTBYel4JeLDTUeCMzj1R4tj9fN9qG49gQ1Ted1ODRgqzw kqGd4d2aqhWaFLwqA+cnhrBqYI8WGs62QNgp317R3iO6dyMWNQiyrI6qkj0FcOJzuI VUYn2KIxHmyeXsdxZvelj2urJcqopPb8MnJ2Y/QQ= Date: Wed, 8 Apr 2020 13:58:30 +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: <20200408135830.25a8e2ef@firost> In-Reply-To: <20200408022345.GC1606@paquier.xyz> 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> Organization: Dalibo MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 8 Apr 2020 11:23:45 +0900 Michael Paquier wrote: > On Tue, Apr 07, 2020 at 05:17:36PM +0200, Jehan-Guillaume de Rorthais wrote: > > I'm not sure who would need this information before the WAL machinery is up, > > but is it safe enough in your opinion for futur usage of > > GetRecoveryState()? Do you think this information might be useful before > > the WAL machinery is set? Current "user" (eg. restoreTwoPhaseData()) only > > need to know if we are in recovery, whatever the reason. > > (I had this thread marked as something to look at, but could not. > Sorry for the delay). (no worries :)) > > src/test/recovery/t/011_crash_recovery.pl | 16 ++++++++++++++-- > > 1 file changed, 14 insertions(+), 2 deletions(-) > > > > diff --git a/src/test/recovery/t/011_crash_recovery.pl > > b/src/test/recovery/t/011_crash_recovery.pl index ca6e92b50d..ce2e899891 > > 100644 --- a/src/test/recovery/t/011_crash_recovery.pl > > +++ b/src/test/recovery/t/011_crash_recovery.pl > > @@ -15,11 +15,17 @@ if ($Config{osname} eq 'MSWin32') > > 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.