RE: Disable WAL logging to speed up data loading
От | osumi.takamichi@fujitsu.com |
---|---|
Тема | RE: Disable WAL logging to speed up data loading |
Дата | |
Msg-id | OSBPR01MB488821D9347C14D3F5013209EDFF0@OSBPR01MB4888.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: Disable WAL logging to speed up data loading ("tsunakawa.takay@fujitsu.com" <tsunakawa.takay@fujitsu.com>) |
Ответы |
Re: Disable WAL logging to speed up data loading
|
Список | pgsql-hackers |
Hello On Friday, Nov 20, 2020 9:33 AM Tsunakawa, Takayuki <tsunakawa.takay@fujitsu.com> wrote: > From: Kyotaro Horiguchi <horikyota.ntt@gmail.com> > > At Thu, 19 Nov 2020 11:04:17 -0500, Stephen Frost <sfrost@snowman.net> > > > * Laurenz Albe (laurenz.albe@cybertec.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. Best, Takamichi Osumi
В списке pgsql-hackers по дате отправления: