mikeklaas

> Most weekends rather than recharging for the rest of the week, I end up more tired than I started.

As a parent, it's hard to remember that ending a weekend "recharged" is a common experience.

There are projects that use LSMTs as the storage engine for RDBMS' (like RocksDB); I'm not sure it's accurate to say "they can't be use as an RDMBS".

Development apps are exempt from the requirement. (They are also limited to 100 accounts)

Multiple databases in postgres fundamentally share the same underlying infrastructure (i.e., WAL), and so do not offer much in terms of scalability or blast-radius protection compared to putting all tables in the same database.

I'm surprised to see the Portal listed. We have one for letting the grandparents talk to the kids, and it is the most unreliable piece of technology I've owned. Constant connection issues and laggy UI.

whoa, do you have a link?

That's probably the worst book in the series.

> And it can't be adjusted on the fly, per query.

Sure it can:

   SET LOCAL work_mem = '256MB';
   SELECT * FROM …

I find it pretty odd to speculate that they are experiencing a very specific failure mode of a particular database. Do you even know whether they use Postgres?

Do you have a source for that?

The "good reason" is that considering 12am the "middle of the day" only makes sense if the typical sleeping window was 8pm to 4am (making midnight the "middle of the night").

Adding a NULL constraint isn't zero downtime since PG scans the whole table ensuring that the constraint is not violated.

Perhaps I misinterpreted this part?

> I struggle to consider using it as a data store these days as well with other options on the table.

It sounds like you wouldn't use it for any purposes.

What would you use redis for, if anything?