🎉 Hold onto your keyboards, folks! Postgres 19 is here with "not-really-hints" query hints 😂. Apparently, calling them hints would be too mainstream for the oh-so-elite Postgres community 🙄. Prepare for the "mass hysteria" of developers pretending this is groundbreaking 🚀.
https://www.pgedge.com/blog/looking-forward-to-postgres-19-query-hints #Postgres19 #queryhints #developerhumor #databaseupdates #technews #HackerNews #ngated
Looking Forward to Postgres 19: Query Hints

Postgres 19 brings plan advice: the query hints the Postgres community held off on for 15 years. Shaun Thomas covers the 15-year debate, pg_plan_advice, pg_stash_advice, and how to use them.

Looking Forward to Postgres 19: Query Hints

Postgres 19 brings plan advice: the query hints the Postgres community held off on for 15 years. Shaun Thomas covers the 15-year debate, pg_plan_advice, pg_stash_advice, and how to use them.

Postgres marks dead tuples reusable after VACUUM - it doesn't free them to the OS. VACUUM FULL does, but holds an ACCESS EXCLUSIVE lock the whole time. On a large #PostgreSQL table in production, that's a non-starter.

#Postgres19 introduces REPACK CONCURRENTLY 🔧 In-core rewrites, lock held only during the final swap. Demo: 138 MB → 52 MB, returned to OS.

REPACK USING INDEX physically reorders rows: 3,300 buffer reads → 49, 3ms → 0.6ms. Shaun Thomas walks through both.

https://www.pgedge.com/blog/looking-forward-to-postgres-19-the-new-repack-command