home.social

#postgres19 β€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #postgres19, aggregated by home.social.

fetched live
  1. πŸŽ‰ Ah yes, Postgres 19, the mythical creature we have all been waiting for, like a database unicorn. Apparently, we need it to answer burning questions like "What was your data wearing last Tuesday?" πŸ•΅οΈβ€β™‚οΈ With cutting-edge features from 2011, we'll finally be able to relive the thrilling days of yore, one SQL query at a time! πŸš€
    pgedge.com/blog/looking-forwar #Postgres19 #DatabaseUnicorn #SQLQueries #TechHumor #CuttingEdgeFeatures #HackerNews #ngated

  2. πŸŽ‰ Ah yes, Postgres 19, the mythical creature we have all been waiting for, like a database unicorn. Apparently, we need it to answer burning questions like "What was your data wearing last Tuesday?" πŸ•΅οΈβ€β™‚οΈ With cutting-edge features from 2011, we'll finally be able to relive the thrilling days of yore, one SQL query at a time! πŸš€
    pgedge.com/blog/looking-forwar #Postgres19 #DatabaseUnicorn #SQLQueries #TechHumor #CuttingEdgeFeatures #HackerNews #ngated

  3. πŸŽ‰ 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 πŸš€.
    pgedge.com/blog/looking-forwar #Postgres19 #queryhints #developerhumor #databaseupdates #technews #HackerNews #ngated

  4. πŸŽ‰ 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 πŸš€.
    pgedge.com/blog/looking-forwar #Postgres19 #queryhints #developerhumor #databaseupdates #technews #HackerNews #ngated

  5. 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.

    pgedge.com/blog/looking-forwar

  6. 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.

    pgedge.com/blog/looking-forwar