kaamos

4 ms·

1.
by kaamos 9y ago
It is, in fact sensible without Enterprise Edition. The only thing it says is that page-level encryption in Community Edition is not intended as a regulatory compliance solution. Nothing more, nothing less. Even in case you care about regul
2.
by kaamos 9y ago
Does that comment say I'm listing features only available in MySQL Enterprise Edition?
3.
by kaamos 9y ago
Let me just tell you that I've read both links before.
4.
by kaamos 9y ago
No, this is all from MySQL Community Edition.
5.
by kaamos 9y ago
Without O_DIRECT, the page may be updated multiple times in the page cache before it hits the disk. The only thing PostgreSQL can do is to update the checksum before expelling the page from its own cache, so it will be doing unnecessary wor
6.
by kaamos 9y ago
True, but then you can sing a similar song about PostgreSQL being the kind of guy that is cool all around, and is always there for that high school sweetheart, but still that badass MySQL gets all the fun and is always center of the party,
7.
by kaamos 9y ago
OK, I see it now, thanks. I would even edit my original comment if I could. Still, the original article is biased without mentioning strict mode, the fact that it's been recommended to turn it on in any serious deployment for years, an
8.
by kaamos 9y ago
It's just something I care about. You may call me an evangelist if you like, I consider myself an anti-evangelist.
9.
by kaamos 9y ago
Data integrity is of course important, and MySQL indeed has a weak story here, especially in older versions. Is PostgreSQL flawless when it comes to data integrity? No, that would also be false advertising. Some examples: - data checksums a
10.
by kaamos 9y ago
> Nearly everything else in Postgres is set-it-and-forget-it. There are many people who would disagree with that. Talking to Uber engineers would probably be a good idea to dispel that myth.
11.
by kaamos 9y ago
I know what I'm talking about. Over the last couple of years I had to speak to many people in the PostgreSQL community. While there are indeed many smart and nice people with balanced views and opinions there, the majority has this ide
12.
by kaamos 9y ago
Agree, I might have misread the discussion. However, strict mode is on my default since MySQL 5.7 (released in 2015) and MariaDB 10.2 (which is also the version he was using). So he changed that, but didn't explicitly state it. Even wh
13.
by kaamos 9y ago
The guy has deliberately changed a default setting (sql_mode) to make MariaDB/MySQL look worse. When someone pointed that out in the comments, he left it unresponded. Which is already telling something about PostgreSQL evangelism. Spea
14.
by kaamos 11y ago
Oh yes, we should: https://bugs.mysql.com/bug.php?id=76927