andrioni

It's a ZDF documentary, I imagine DW only got the rights to show the translation outside of Germany.

Here's a link to the original: https://www.zdf.de/video/dokus/megacitys-wenn-es-nacht-wird-...

You can just pay extra for extended or infinite retention. https://www.backblaze.com/cloud-backup/features/extended-ver...

One use case where it would be beneficial is for tables that have batch-style patterns, where you (at least in my experience) need to provision a good enough baseline before autoscaling kicks in.

In some cases I've seen, autoscaling can manage going from ~500 to 10k WCU without heavy throttling (as the burst capacity can handle the five~ten minutes before autoscaling kicks in), but not with a smaller baseline. On tables with hot shards, the baseline usually has to be higher.

It's not entirely uncommon in mathematics to see citations to "personal communication with [insert name of other mathematician here]".

This kind of clause is usually known as a "DeWitt clause"[1], after a University of Wisconsin professor who benchmarked a couple databases, including Oracle (which performed poorly). Oracle/Larry Ellison didn't react well to that and decided to forbid benchmarks.

[1]: https://danluu.com/anon-benchmark/

Does it mean it will be possible to use EdgeDB with hosted Postgres databases, like RDS and maybe Amazon Aurora (on Postgres mode)?

Is EdgeDB going to be Postgres fork, extension or a service that uses just uses Postgres as a storage layer (like Datomic)?

It seems more similar in spirit to triplestores, which are pretty neat all things considered. It also reminds me a lot of Datomic, but without the Clojure-ness and immutability.

44 million, according to their paper, and they used 5000 TPUs, which are capable of 4.6×10^17 operations per second.

(The operations the TPU can run are far simpler than what supercomputers can do, but just for the sake of comparison, the current top supercomputer in the world can do 1.25×10^17 floating point operations per second)