PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
1 patchset tracked - current t38453_149
v149t38453_149posted Apr 10, 2018successwon't retryancient 8ypg 11
baseda9b580d8 Apr 07, 2018 - 3087 days / 20694 commits behind master (from history)
applyapplied Jul 26, 07:32
pushJul 27, 20:32 -> ad792536abranchdiff vs base
| Result | Att | PG | Tests | Build / test | Image | When |
|---|---|---|---|---|---|---|
| success | 1 | 11 | 509 / 509 | 1m 49s / 2m 51s | docker run ... :t38453 | Jul 27, 20:42 |
run 30303021006executed 509 - ccache 129 hit / 4886 miss - head ad792536a - digest sha256:ca8cdd5432fb02... - run 30303021006 | ||||||