Not being owned by Oracle?
Why PostgreSQL is better than MySQL
81–90 of 100 posts
Re: Why PostgreSQL is better than MySQL
#82Earlier quoted context omitted.
I remember ages ago (a decade? or so?) I started working at a company using Postgres for a project, and one of the things my boss asked me to do was to set up replication for the database. We had it on all of our MySQL databases, and everyone knew (myself included) that Postgres was a more serious, enterprise-y, "real" database. Well, I googled around and couldn't find anything conclusive, so I hopped into the / chan…
So why is replication necessary?
HA, Read load balancing for a simple master-slave setup.
Re: Why PostgreSQL is better than MySQL
#83Earlier quoted context omitted.
Uber had a pretty good argument not long ago on going from Postgres back to MySQL: https://eng.uber.com/mysql-migration/
Ahhh Uber, the leading light on how to do things right.
I've never worked at that scale - I doubt many have. I am sure that all manner of incorrect decisions are required to make that level of scale work.
What is the reddit thread that almost broke them? This one I think: https://www.reddit.com/r/pics/comments/92dd8/test_post_pleas...
From memory, they do something different for just that thread, like loading it from a different cache. I am sure that is all sorts of "wrong", but being "right" and not scaling seems worse!
Re: Why PostgreSQL is better than MySQL
#84I had hoped that this article will illustrate the scientific/technical reasons for PostgreSQL's superiority over MySQL. Alas, it just mentions that there was a bug that got fixed after 14+ years in MySQL. The author doesn't even mentions the severity of the bug and the negative effects it had. Overall, for me this article is nothing but the author just "blowing his/her own horn".
Re: Why PostgreSQL is better than MySQL
#85What about Postgres DBAs? I don't see too many of those around to allow Postgres to be picked up more....
Re: Why PostgreSQL is better than MySQL
#86I'm a huge Postgres fan and yes I'm probably biased towards it. I do think it's probably the best open source database out there, but I also don't love these types of posts. What makes something better than another things is a whole host of things, not just highlighting one really bad case from the other side. I'm sure if the MySQL world wanted they could point out ways that MySQL is so much better than Postgres. Jus…
I remember ages ago (a decade? or so?) I started working at a company using Postgres for a project, and one of the things my boss asked me to do was to set up replication for the database. We had it on all of our MySQL databases, and everyone knew (myself included) that Postgres was a more serious, enterprise-y, "real" database. Well, I googled around and couldn't find anything conclusive, so I hopped into the / chan…
You switched to MySQL then?
Re: Why PostgreSQL is better than MySQL
#87Earlier quoted context omitted.
I remember ages ago (a decade? or so?) I started working at a company using Postgres for a project, and one of the things my boss asked me to do was to set up replication for the database. We had it on all of our MySQL databases, and everyone knew (myself included) that Postgres was a more serious, enterprise-y, "real" database. Well, I googled around and couldn't find anything conclusive, so I hopped into the / chan…
As a Postgres fan, I do agree that the Postgres community has a more "RTFM attitude" than MySQL's. I personally don't have a problem with this, but I can understand that it might steer some people away.
"You don't need it" attitude is much worse than RTFM one, especially when the manual actually has a solution.
Re: Why PostgreSQL is better than MySQL
#88Earlier quoted context omitted.
You're wrong, and interestingly, you're omitting the key part: > Such statements produce a warning in the error log when using statement-based mode and are written to the binary log using the row-based format when using MIXED mode The problem you're writing about is not related to MySQL itself, it's a problem implicit in statement-based replication. Row/mixed mode replication has been available in MySQL since 5.1 (al…
You do realize that I didn't write "insanity", right? All I said is "can have fun results". In any case, there are two issues described in my post.
Apologies if I confusingly replied to two posts in one, but there is common thread between the two, that is, a judgement on a product/feature, based on a radically uninformed knowledge of the subject.
I've spent a few minutes after a Google search; results follow.
Bug #11765650: this was fixed 5 and half years ago; see https://lists.mysql.com/commits/143383;
Bug #58637: see https://bugs.mysql.com/bug.php?id=58637 -
this is not a bug; statement-based replication is obsolete, and it's superseded by mixed-mode - if users insist on using the former, they're asking for trouble.
Re: Why PostgreSQL is better than MySQL
#89Earlier quoted context omitted.
I remember ages ago (a decade? or so?) I started working at a company using Postgres for a project, and one of the things my boss asked me to do was to set up replication for the database. We had it on all of our MySQL databases, and everyone knew (myself included) that Postgres was a more serious, enterprise-y, "real" database. Well, I googled around and couldn't find anything conclusive, so I hopped into the / chan…
And it was the community that drew me in. Very early in my database career, I was having massive performance problems with my postgres install. I sent a very sharply toned message to the postgres performance mailing list. Within hours of that message, I was trading stack traces with Tom Lane . He was under no obligation to help me; in fact, I was, in hindsight, kinda a dick about it. But he did. You probably can't bu…
Sure you can. TL works for Crunchy Data [https://www.crunchydata.com/] and I suppose he gets involved in solving customer issues.
Re: Why PostgreSQL is better than MySQL
#90This type of shitpost makes the "victim" look better every time.