LoriP (u/LoriP) - Readit News

LoriP commented on The Dead End redmonk.com/sogrady/2022/... · Posted by u/swyx

ttctciyf · 3 years ago

What happened a couple of years ago with MariaDB?

LoriP · 3 years ago

That was a bad explanation on my part, sorry. They are still open source! But they diverged from keeping fully aligned with MySQL developments AFAIK so are no longer a fork/distribution as they are forging their own path.

So I was being unclear, the "until a couple of years ago" was referring to divergence rather than a change in license.

LoriP commented on The Dead End redmonk.com/sogrady/2022/... · Posted by u/swyx

hardwaresofton · 3 years ago

I do want to note Timescale's license is extremely generous:

https://github.com/timescale/timescaledb/blob/main/tsl/LICEN...

There's a marked difference between what they allow you vs Mongo (SSPL) and Elastic (Elastic license) -- see (b).

Also generally the Postgres ecosystem has in general seemingly found a way to strike a balance between creating immense value (point to a F/OSS DB that's better than Postgres) and enabling commercial success (Citus, 2nd Quadrant, EDB, Timescale, Supabase, Neon are all very successful)

I do agree with the overall trend though -- I already think the future is going to be AGPL[0] (but that's based partially on a misunderstanding of what AGPL does).

It remains to be seen if people will cynically make projects open source to start and then switch to something like SSPL/BSL/Elastic later, but the unintentional rug pulls will probably continue for a while.

[0]: https://vadosware.io/post/the-future-of-free-and-open-source...

LoriP · 3 years ago

Thanks for sharing this point of view. For those interested, I wanted to share this blog post that explains the Timescale approach in detail. https://www.timescale.com/blog/building-open-source-business...

Timescale's community manager.

LoriP commented on The Dead End redmonk.com/sogrady/2022/... · Posted by u/swyx

danbmil99 · 3 years ago

I don't see the real problem here. By its nature, FOSS software cannot be monopolized. If party A decides to replace a legit license with one of these commercial source-available licenses, just fork the last commit using the original license and develop from there.

Oh but wait -- the community, the contributors, the users are all attached to the original project. Well, that's competition: make your version better, advertise the licensing issue; poach the original community.

Case in point:

LoriP · 3 years ago

Your case in point dropped off, but Percona (MySQL and MongoDB distributions) and until a couple of years ago MariaDB fell into this category I think.

LoriP commented on TimescaleDB 2.7 vs. PostgreSQL 14 timescale.com/blog/postgr... · Posted by u/carlotasoto

alecco · 3 years ago

How is this on HN frontpage?

LoriP · 3 years ago

folks like to chat about benchmarks

LoriP commented on TimescaleDB 2.7 vs. PostgreSQL 14 timescale.com/blog/postgr... · Posted by u/carlotasoto

znpy · 3 years ago

No mention of ha in the documentation.

I can’t understand whether HA would rely on the standard postgresql tooling or if you have to pay for some kind of enterprise license to get it.

LoriP · 3 years ago

Timescale doesn't charge for any of its software. Revenue comes from providing hosting services that are optimized towards TimescaleDB and PostgreSQL at scale.

The code is source-available, license philosophy is explained in this blog post https://www.timescale.com/blog/building-open-source-business...

That includes the HA implementation, and I think someone else shared the docs for that. Hope this helps.

LoriP commented on Show HN: pg_netstat, a Postgres extension to monitor database network traffic github.com/supabase/pg_ne... · Posted by u/burmecia

jpgvm · 3 years ago

Or just use TimescaleDB which is competitive on most axes but already PG.

LoriP · 3 years ago

Thanks for the mentions (and for using TimescaleDB).

If anyone's curious about TimescaleDB, it's packaged as an extension to Postgres, optimizing for performance, storage, and analysis of time series data. Implementing columnar compression algorithms is a big part of the secret sauce that makes TimescaleDB a popular choice with Postgres and SQL developers. You can read more about that on the Timescale blog (I'm Timescale's community manager btw). https://www.timescale.com/blog/search/?query=compression

If anyone's curious, the youtube channel may be a good place to start, especially this playlist https://www.youtube.com/playlist?list=PLsceB9ac9MHTtM1XWONMR...

LoriP commented on Declining quality of consumer-grade products – 2009 fridge compressor autopsy automaticwasher.org/cgi-b... · Posted by u/userbinator

inferiorhuman · 3 years ago

As I'm in the middle of replacing a one-year-old LG fridge I've been doing a bit of reading. Apparently rotary compressors like this require exceptionally precise tolerances to achieve any manner of reliability.

Thirteen years doesn't strike me as particularly bad. Not great, but not bad. That 80-year-old fridge the repair shop guy is bragging about is almost certainly not an auto defrost unit. So, sure, it's probably close to a modern fridge in power consumption but the tradeoff is you'll have to scrape ice out of it periodically.

https://hbr.org/1989/03/cold-competition-ge-wages-the-refrig...

Edit:

Pretty early on I got a couple wireless temperature probes and used rtl-sdr to pipe the data into a TimescaleDB instance (and slapped Grafana in front of it).

I have no idea what the actual problem was because LG was keen on a refund over a repair. The symptoms were failure to cool and ice buildup on the evaporator getting into the fan and making a racket. The tech diagnosed a bad thermistor which brought the freezer temp during defrost down from 50°F to about 30–40°F. Even though the tech took a steam gun to the evaporator, it took about two weeks before enough ice built up and fell into the fan again. At this point the fridge wasn't getting below 40°F either and my landlord decided to take them up on the refund offer.

Could've been a bad compressor as one of the failure modes is inability to pump refrigerant. The compressor itself sounded like a ringing bell. I stopped caring because nobody at LG cares and they are not positioned to actually service their appliances. It's likely a design flaw they either already know about or don't want to know about. Getting through to a person empowered to do anything is nearly impossible and their techs have a miserable time trying to get parts from their poorly run warehouses. I'm a bit apprehensive that other companies have joined the race to the bottom, but for now LG is solidly in never again territory for me.

LoriP · 3 years ago

Have to say I love this use case of TimescaleDB and Grafana – a perfect example of time series data used for something small and useful to prove a theory. In case anyone's tantalized the TimescaleDB YouTube channel has some great free how-to videos on setting up TimescaleDB and Grafana.

LoriP commented on SQLite Internals: Pages and B-trees fly.io/blog/sqlite-intern... · Posted by u/eatonphil

packetlost · 3 years ago

You could probably do it with BRIN indexes similar to how TimescaleDB handles their time-series hypertables

LoriP · 3 years ago

TimescaleDB is packaged as a postgres extension, there's a GitHub project here if anyone is interested to check in on that https://github.com/timescale/timescaledb

LoriP commented on PostgreSQL views and materialized views and how they influenced TimescaleDB timescale.com/blog/how-po... · Posted by u/od0

Inviz · 3 years ago

It’s sad that timescale aggregates don’t work on top of other aggregates. Abstractions is leaking. The ticket is left unaddressed for a while

LoriP · 3 years ago

Hello would like to check in on this with you. You can find my email address in my profile, I am Timescale's community manager. Thanks!