jerryjerryjerry

Emm, I'm very curious about the reasons why they finally chose TiDB.

There are some other options as well, like this one: https://www.pingcap.com/tidb-serverless/

Architecturally yes but with an extension of in-memory columnar format as well. This makes it an HTAP (Hybid Transactional and Analytical Processing) database.

Wow, this is a very nice tool! Although I'm a ReMarkable2 user, I'm also curious about if this tool can be extended to support the newly launched Kindle Scribe.

In general, NewSQL (distributed database) may still be a good solution to address scalability limit encountered by a single server/node database like MySQL/PG. Currently, there are quite a few options in this domain: Spanner, PG-compatible (CockroachDB, YugaByte), MySQL-compatible (TiDB, MariaDB xPand), and other middleware products to handle sharding.

Nice find, I like it!

"The data was stolen from a misconfigured cloud database found by the attacker through a search engine"

Thanks for sharing. I also found their blogs are insightful as well and worthy reading.

I like the subtitle LOL: "Big Red doesn't charge more when users add cores, so Big Blue plans to triple the count. Because why not?"

Several other alternatives: https://stackdiary.com/figma-alternatives/

To save you extra search and clicks, here are their github https://github.com/penpot/penpot and open source insight data https://ossinsight.io/analyze/penpot/penpot

Looking at the failed queries, yes, OOM might be one big factor due to aggregations (there is no join in these queries though).

My wild guess is lack of some functions, e.g., regexp, but need to take a deep look.

LOL

Good point but I think that's fine ;-) curious about answers...

Sigh invite only :-( wondering when this fantastic keyboard goes public for sale...

Very nice, and thanks for sharing!

oh man, I'm also typing on my T440p now, and yes, it's still running strong and healthy without much to complain.

Same here, and I'd also like to see what explain analyze shows about the plan and execution details. Also, some system setup may also help, e.g., memory size and check if spill kicks in, etc.

ASIMO was once amazing technology and showcase of robot, but quite quiet for quite awhile...

wow, lots happened in just one single day... thanks and voted

"sorry we couldn't find that page"...

RIP. Some of my friends tweeted this sad news but I myself am not familiar with his work though..

TL;DR “....hoodies provide more than just physical comfort; they administer emotional comfort, too, similar to that of a weighted blanket.”

FYI, you are 1 day late, but yes, this is a truly funny story :-)

https://news.ycombinator.com/item?id=32351067

Same here.

Yes, definitely it may help if going with multiple clusters, however, there are also many scenarios that we don't want to maintain multiple clusters. For example, when we come to a SaaS platform, multi-tenant is pretty typical where different tenants may have different workloads, and workload management would be needed for different users, or even within the same tenant. So the "built-in" workload management (besides other features for multi-tenant) would be a big plus.

One of the features I'm interested in (or would like to have) from Trino or Presto is the workload management which can better manage different types of queries and allocate resources accordingly. This becomes important when more applications adopt Trino or Presto as a distributed SQL database/platform, where the impact from different queries or workloads can be mitigated, besides the dedicated resources (CPU, MEM, etc.) can be allocated to high priority workloads. I'm really wondering if/when such capabilities may be provided.

BTW, purely curiosity, I compared Trino with Presto from OSS point of view (https://ossinsight.io/analyze/prestodb/presto?vs=trinodb%2Ft...), both communities are still popular but Trino seems more active than Presto now. I also wonder if two communities may reunion someday again to really boost its impact (comparing to Spark community).

Very informative, thanks for sharing. I guess one of the assumptions behind this is the overall economy is good so the private companies can raise funding easily without going public. Emm but on a second thought, it shouldn't matter when economy is good as companies can always raise funding easily no matter from private equality or public, vice versa, companies may find challenging to raise money when economy is downturn no matter from private or public. So, maybe what you mentioned are the main reasons.

That's 0.39%, not sure if this is typical but seems pretty low to me. Anything we can learn from this number, or it's simply just a number?