#caching

1 post on this topic, newest first. all tags →

Cache Components changed how I think about a page

Next.js 16 swapped the route level caching knobs for one directive, and 16.3 took it to the client for instant navigations. I migrated a content site and a dashboard. One got faster with almost no work. The other made me admit what a 'page' had been hiding the whole time.

nextjsreactcaching+1 more

Jun 9, 20269 min11 min

~/tips/today — 2026-10-19

~cat tips/today

Never build an index on a live table without CONCURRENTLY

postgresqlmigrations

A plain CREATE INDEX takes a lock that blocks every write to the table for the whole build. On a big table that means minutes of outage that look like a hung app.

CREATE INDEX CONCURRENTLY orders_customer_idx ON orders (customer_id);

It's slower and can't run inside a transaction, so you'll have to tell your migration tool. If it fails halfway, it leaves an invalid index behind, so check pg_index.indisvalid and drop it before you retry.

↵ open y yesterday l ls /tips

esc close