Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
evanelias
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
evanelias
8mo ago
Ditto here, season 9 ("Back to Earth") is the only one I have no desire to rewatch. Season 12 is particularly good though. In my opinion, the first and last episodes of that season are among the funniest they've ever done!
92.
▲
by
evanelias
8mo ago
Yeah the first two novels were credited to their "Grant Naylor" partnership, and they're both excellent. After that, they each wrote an additional Red Dwarf novel individually / separately. Personally I've never com
93.
▲
by
evanelias
8mo ago
> So many quotable moments. Vantasner Danger Meridian. Structural Dynamics of Flow. The attaché badge. My friends and I have found that Patriot phrases make excellent team names in pub trivia, even if no other teams get the references. (
94.
▲
by
evanelias
8mo ago
Ha, I was just about to comment the same! It's strangely compelling and very memorable. And all of Peaks Island is quite scenic, makes a great summer day trip from Portland Maine.
95.
▲
by
evanelias
8mo ago
> something that needs to run on top of a Petabytes of data in the cloud, on Iceberg, with an advanced query planner and a high speed SIMD engine Part of my confusion was that this blog post makes no mention whatsoever of any of those th
96.
▲
by
evanelias
8mo ago
This sounds conceptually similar to performance_schema [1] in MySQL or MariaDB, which is a built-in feature originally introduced in MySQL 5.5 (2010). Or perhaps the easier-to-use sys schema [2], which wraps performance_schema among other t
97.
▲
by
evanelias
8mo ago
> foreign key cascades where not in the binlogs. True, but that's finally solved now. > I also think that some changes in the database layout could lead to strange things on the replicas. I've been using MySQL for 23 years a
98.
▲
by
evanelias
8mo ago
InnoDB became the default storage engine over 15 years ago. MyISAM is barely used by anyone today. What "strange stuff around replication" are you referring to?
99.
▲
by
evanelias
8mo ago
You can tune binlog_expire_logs_seconds to control how long old binlog files stay around. The default is 2592000 seconds (30 days) which is often too long.
100.
▲
by
evanelias
8mo ago
The sync_binlog server variable controls this behavior. The default of 1 means to fsync every time, which is best for durability but worst for performance. See https://dev.mysql.com/doc/refman/8.4/en/repl
101.
▲
by
evanelias
8mo ago
OK, but that makes perfect sense given utf-16 was actually quite widespread in 2003! For example, Windows APIs, MS SQL Server, JavaScript (off the top of my head)... these all still primarily use utf-16 today even. And MySQL also supports u
102.
▲
by
evanelias
8mo ago
The performance impact depends substantially on whether you've configured it to fsync the binlog on every group commit. Also, it's important to consider that replication and backups serve different purposes. Backups alone are insu
103.
▲
by
evanelias
8mo ago
They should have addressed it much earlier, but it makes way more sense in historical context: when MySQL added utf8 support in early 2003, the utf8 standard originally permitted up to 6 bytes per char at that time. This had excessive stora
104.
▲
by
evanelias
8mo ago
That's an absolutely ridiculous assertion. Do you similarly think that the Battlestar Galactica reboot was a thinly-veiled racist show because they frequently called the Cylons "toasters"?
105.
▲
by
evanelias
8mo ago
Well, that certainly explains why no one in the US telnet BBS community seemed to be discussing having connectivity problems.
106.
▲
by
evanelias
8mo ago
Right, but my point was that renames in particular typically can't go out well before the corresponding application change [1]. Thus, renames are "out of band" relative to the company's normal schema change process. (T
107.
▲
by
evanelias
9mo ago
pgroll is definitely interesting; it overlaps between both schema management tools and online schema change tools. At scale, I would want to have a better understanding on the performance implications of putting views in front of hot tables
108.
▲
by
evanelias
9mo ago
> I don't understand how you can run multiple postmasters. I believe they're just referring to having several completely-independent postgres instances on the same host. In other words: say that postgres is maxing out at 2000 c
109.
▲
by
evanelias
9mo ago
The major players tried teaming up 12 years ago but it didn't work out: https://en.wikipedia.org/wiki/WebScaleSQL The general response from the community often included complaints of there being too much fragmenta
110.
▲
by
evanelias
9mo ago
Not sure what that means, but it's named partially as a nod to Skee-Ball. The town I grew up in was actually the home of the factory where all Skee-Ball machines were made. I was using a location-related naming scheme in general at tha
111.
▲
by
evanelias
9mo ago
For both data migrations and renames, there isn't really a one-size-fits-all solution. That's actually true when doing data changes or renames in imperative (incremental) migrations tools too; they just don't acknowledge it,
112.
▲
by
evanelias
9mo ago
Thank you for the kind words about Skeema!
113.
▲
by
evanelias
9mo ago
Very large tech companies completely automate the schema change process (at least for all common operations) so that development teams can make schema changes at scale without direct DBA involvement. The more sophisticated companies handle
114.
▲
by
evanelias
9mo ago
Also check out ProxySQL [1][2], it's an extremely powerful and battle-tested proxy. Originally it was only for MySQL/MariaDB, where it is very widely used at scale, even despite MySQL already having excellent built-in scalable thr
115.
▲
by
evanelias
9mo ago
For schema changes, it absolutely can, for every situation except table renames or column renames. That might sound like a major caveat, but many companies either ban renames or have a special "out-of-band" process for them anyway
116.
▲
by
evanelias
9mo ago
The manual is still quite comprehensive, but their doc updates seemingly went off the rails during the switch to quarterly "Innovation" releases starting with MySQL 8.1, and never really recovered. They keep forgetting to update v
117.
▲
by
evanelias
9mo ago
That's totally fine, there are many workloads where Postgres is the best choice! I'm not forcing you to use it, I was just responding to the comment upthread about lack of advantages. It's kind of bonkers that the anti-MySQL
118.
▲
by
evanelias
9mo ago
Be sure to look at the actual sqldef command-line tool, not the trivial copy-and-paste demo on their website. Declarative schema management is best used combined with a Git repo. In the big picture, declarative schema management has lots of
119.
▲
by
evanelias
9mo ago
Personally I've always called this style "declarative schema management" since the input declares the desired state, and the tool figures out how to transition the database to that state. sqldef is really cool for supporting
120.
▲
by
evanelias
9mo ago
A few major areas where MySQL/MariaDB excels: Threaded connection model (no process spawning) Undo-based MVCC (no need for vacuum) InnoDB's use of a clustered index for PK (has pros/cons, but better for some workloads) Abilit
More ›