News for hackers. Stuff that matters.

A comment on PostgreSQL used fsync incorrectly for 20 years. Parent comment

Re:PostgreSQL used fsync incorrectly for 20 years by lugg on Sunday February 10, 2019 @05:35AM (#19127223)
You had me until you tried to justify bubbling the error instead of handling it at its source while possible.
[ Parent | on HN ]
Re:PostgreSQL used fsync incorrectly for 20 years by naasking on Sunday February 10, 2019 @09:19AM (#19127844)
That can be a correct response, for instance, if you have some sort of async i/o in place so you don't want to wait for a write that's not ready because you'll block.
[ Parent | on HN ]
Re:PostgreSQL used fsync incorrectly for 20 years by anarazel on Sunday February 10, 2019 @05:47AM (#19127250)
Hm? I explicitly said that retries would be better?
[ Parent | on HN ]