PostgreSQL used fsync incorrectly for 20 years

Re:PostgreSQL used fsync incorrectly for 20 years by marcinzm on Sunday February 10, 2019 @05:22PM (#19130479)

>Telling them “no” isn’t going to make them focus instead on the project leadership’s other priorities like it would in a corporate team.

No one is asking them to. An open source project is not a corporation, it has no shareholders who require growth at all costs. So someone doesn't contribute to the project, if there's enough other contributors to keep it healthy then who care? No need to try and get every single potential contributor to contribute code to the project.

[ Parent | on HN ]

Re:PostgreSQL used fsync incorrectly for 20 years by closeparen on Sunday February 10, 2019 @10:15PM (#19131799)

You can’t pay an opportunity cost on an opportunity you don’t have. Whatever the reason for rejecting the patch in this case, it is not a missed opportunity to work on bugs and tech debt as suggested by the parent.

[ Parent | on HN ]