Why Postgres wants NVMe on the hot path, and S3 everywhere else | Dark Hacker News