PostgreSQL used fsync incorrectly for 20 years

Re:PostgreSQL used fsync incorrectly for 20 years by sqldba on Sunday February 10, 2019 @03:58AM (#19126977)

Try committing to a Microsoft open source project or working with a lot of ex-Microsoft employees. You’ll want to kill yourself.

[ Parent | on HN ]

Re:PostgreSQL used fsync incorrectly for 20 years by DoofusOfDeath on Sunday February 10, 2019 @12:31PM (#19128790)

It sounds like you have an interesting anecdote to share.

If you can just give us the anecdote rather than making a vague, sweeping critique of MS OSS projects, you might avoid the downvotes.

[ Parent | on HN ]

Re:PostgreSQL used fsync incorrectly for 20 years by GordonS on Sunday February 10, 2019 @10:29AM (#19128111)

I've had this experience when I've tried to contribute to ASP.NET Core and .NET Core - in the case of ASP.NET Core, they weren't in the slightest bit interested in fixing something that's obviously broken. In the case of .NET Core, it was made clear that adding something new to the encryption library was going to take a long time, possibly years, even though there was demand for it.

I've given up on both :/

[ Parent | on HN ]

Re:PostgreSQL used fsync incorrectly for 20 years by faical on Sunday February 10, 2019 @05:43AM (#19127242)

<off-topic>I committed to a Microsoft open source project and worked with (ex-)Microsoft people. The experience was great :)</off-topic>

[ Parent | on HN ]