A failed read must throw, not return 0 — how Next.js ISR bakes your fallback into the cache

I run a directory site: ~3,500 rows in Postgres, read over PostgREST, rendered by Next. js with revalidate on every route. The headline number in the shell says "Search all 3,516 listings.

Source: [Dev.to](https://dev.to/kynth/a-failed-read-must-throw-not-return-0-how-nextjs-isr-bakes-your-fallback-into-the-cache-57in)