Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
В списке pgsql-hackers по дате отправления:
| От | Andres Freund |
|---|---|
| Тема | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Дата | |
| Msg-id | 20180409203415.spd3nkv752r6q7df@alap3.anarazel.de обсуждение |
| Ответ на | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS (Mark Dilger <hornschnorter@gmail.com>) |
| Список | pgsql-hackers |
Hi, On 2018-04-09 13:25:54 -0700, Mark Dilger wrote: > I was reading this thread up until now as meaning that the standby could > receive corrupt WAL data and become corrupted. I don't see that as a real problem here. For one the problematic scenarios shouldn't readily apply, for another WAL is checksummed. There's the problem that a new basebackup would potentially become corrupted however. And similarly pg_rewind. Note that I'm not saying that we and/or linux shouldn't change anything. Just that the apocalypse isn't here. > Your comment reads as if this is a problem isolated to whichever server has > the problem, and will not get propagated to other servers. Am I reading > that right? I think that's basically right. There's cases where corruption could get propagated, but they're not straightforward. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера