News for hackers. Stuff that matters.
Re:Notes on concurrency bugs by spudlyo on Friday August 05, 2016 @11:52PM (#12236945)
Why are these academic types analyzing bugs in MySQL!? Is there a reason they didn't choose PostgreSQL, or is it just because these studies were all done in 2009 and 2010? Surely if the analysis would have been done in 2016 they would have picked a database with higher quality concurrency bugs to study.
Re:Notes on concurrency bugs by v4tk on Saturday August 06, 2016 @12:23AM (#12237009)
PostgreSQL does not have bugs - there is even no bugtracker https://lwn.net/Articles/660468/ . It is hard to analyze bugs if there is no central place for them.
Re:Notes on concurrency bugs by jacquesm on Saturday August 06, 2016 @04:33AM (#12237520)
> PostgreSQL does not have bugs

What a nonsense. Postgres has over 14K issues listed against it, they just don't use a bug tracker, they use a mailing list instead. It's a holdover from the old days.

https://www.postgresql.org/list/pgsql-bugs/2016-07/

Re:Notes on concurrency bugs by nl on Saturday August 06, 2016 @07:36AM (#12237783)
You mean like the bit where he says "That’s interesting, but it’s hard to tell from that if the results generalize to projects that aren’t databases, or even projects that aren’t MySQL." and then points to a study which finds the same kind of problems across a number of different projects?