From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, masao(dot)fujii(at)oss(dot)nttdata(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: [BUG] non archived WAL removed during production crash recovery |
Date: | 2020-04-22 14:14:20 |
Message-ID: | 20200422161420.1e82be3d@firost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Wed, 22 Apr 2020 10:19:35 +0900
Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Apr 22, 2020 at 12:41:21AM +0200, Jehan-Guillaume de Rorthais wrote:
> > Do we need to acquire info_lck to look at the state here, as we do in
> > GetRecoveryState()? Why is it missing from previous code where
> > SharedRecoveryInProgress was protected by info_lck as well?
>
> Please see 1a3d104.
Understood. Interesting. Thank you.
> > Plus, the new line length overflow the 80-column, but I'm not sure where to
> > break this line.
>
> pgindent has been run on v8, and it did not complain.
OK.
> > In fact, this was inherited from 011_crash_recovery.pl where I originally
> > added some tests. As 020_archive_status.pl doesn't use IPC::Run, the
> > comment is wrong. But I wonder if this whole block is really needed.
> > Unfortunately I can't test on MSWin32 :/
>
> You are right here. The restriction can be removed, and I have
> checked that the test from v8 is able to pass on my Windows dev VM.
Thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | John Muehlhausen | 2020-04-22 15:38:11 | Re: NOTIFY in multi-statement PQexec() not sent outside of transaction |
Previous Message | Arthur Nascimento | 2020-04-22 12:15:01 | Re: BUG #16380: documentation: host[no]gssenc vs. address/IP-address/IP-mask fields |
From | Date | Subject | |
---|---|---|---|
Next Message | Jesse Zhang | 2020-04-22 14:17:05 | Header / Trailer Comment Typos for M4 macros |
Previous Message | Ranier Vilela | 2020-04-22 14:06:29 | Re: PG compilation error with Visual Studio 2015/2017/2019 |