Re: Disable WAL logging to speed up data loading

Greetings,

* osumi(dot)takamichi(at)fujitsu(dot)com (osumi(dot)takamichi(at)fujitsu(dot)com) wrote:
> On Friday, Nov 20, 2020 9:33 AM Tsunakawa, Takayuki <tsunakawa(dot)takay(at)fujitsu(dot)com> wrote:
> > From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
> > > At Thu, 19 Nov 2020 11:04:17 -0500, Stephen Frost <sfrost(at)snowman(dot)net>
> > > > * Laurenz Albe (laurenz(dot)albe(at)cybertec(dot)at) wrote:
> > > > > I missed that this is only a warning when I looked at it before.
> > > > > Yes, it should be a fatal error.
> > > >
> > > > Yeah, the more that I think about it, the more that I tend to agree
> > > > with this. Does anyone want to argue against changing this into a
> > FATAL..?
> > >
> > > I don't come up with a use case where someone needs to set
> > > wal_level=minimal for archive recovery. So +1 to change it to FATAL.
> It seems we reached the agreement for this fix.
>
> > Thank you all. I'd like to give Osumi-san an opportunity to write a patch and
> > showing the evidence of successful test if you don't mind. He is very young
> > and newbie to Postgres, so even a small contribution would encourage him to
> > make further contributions.
> Sure. Let me do that, including the test.

That all sounds good to me. I would recommend starting a new thread on
-hackers with the patch, once it's ready, since it's really independent
from the topic of this thread.

Thanks,

Stephen