PostgreSQL pain points

Posted Mar 26, 2014 12:52 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)
In reply to: PostgreSQL pain points by kev009
Parent article: PostgreSQL pain points

I was kinda expecting to read something like: "There was a meeting of PostgreSQL and kernel developers. There were no survivors of the bloodbath that had ensued".

PostgreSQL pain points

Posted Mar 27, 2014 15:00 UTC (Thu) by smitty_one_each (subscriber, #28989) [Link] (8 responses)

"All went swimmingly until a kernel dev jokingly suggested mySQL as a work-around. . ."

PostgreSQL pain points

Posted Mar 28, 2014 21:25 UTC (Fri) by bronson (subscriber, #4806) [Link] (7 responses)

... and a Postgres dev retorted that FreeBSD didn't exhibit any of these problems.

PostgreSQL pain points

Posted Apr 3, 2014 9:54 UTC (Thu) by Pawlerson (guest, #74136) [Link] (6 responses)

Use Linux and MySQL. Problems solved. If PostgreSQL has problems its developers should solve them. If they care..

PostgreSQL pain points

Posted Apr 3, 2014 14:24 UTC (Thu) by olgeni (guest, #96387) [Link]

Use FreeBSD and PostgreSQL. Problems solved, and you also get a proper database for free.

PostgreSQL pain points

Posted Apr 3, 2014 18:31 UTC (Thu) by dlang (guest, #313) [Link] (1 responses)

you act as if MySQL doesn't run into the same problems. I think you just don't understand the details well enough.

PostgreSQL pain points

Posted Apr 3, 2014 18:32 UTC (Thu) by mathstuf (subscriber, #69389) [Link]

MySQL avoids the problem by just dropping your data instead ;) . You prefer fast over correctness, right?

PostgreSQL pain points

Posted Apr 3, 2014 20:22 UTC (Thu) by rodgerd (guest, #58896) [Link]

And instead you get the problem of your data being quietly corrupted.

PostgreSQL pain points

Posted Apr 4, 2014 6:10 UTC (Fri) by palmer_eldritch (guest, #95160) [Link] (1 responses)

I think you missed the joke here...

PostgreSQL pain points

Posted Apr 7, 2014 13:22 UTC (Mon) by nix (subscriber, #2304) [Link]

He also missed the point -- that these are problems which *cannot* be solved by the PostgreSQL developers alone; not without implementing what amounts to an operating system inside the database (as some other big database vendors do, and they all hate it).