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 emilsedgh on Sunday February 10, 2019 @04:26PM (#19130146)
It's not at simple as that.

The patch author does the "initial" work. But then it's up to the team to learn the patch, understand it and keep maintaining it.

Every line of code is baggage.

If there is no demand for something at the time, it makes sense for maintainers to reject that. It's up to them to maintain that patch from now on.

[ Parent | on HN ]
Re:PostgreSQL used fsync incorrectly for 20 years by ospider on Monday February 11, 2019 @03:42AM (#19132915)
There is another scenario, I submitted a Pull Request to a OSS project, the authors discussed it and rejected it and then implemented it in the exact same way as I did. That was hurtful.
[ Parent | on HN ]
Re:PostgreSQL used fsync incorrectly for 20 years by darkerside on Monday February 11, 2019 @11:43AM (#19135762)
I can't upvote your comment for some reason, but exactly this
[ Parent | on HN ]