‹ BackHN Continuity

Thread

Training a 4B model to produce 81% faster query plans than Postgres

702 points · 144 comments · polyphilz

  1. zacmps · · focus · HN ↗
    I am skeptical of these results given that the end has:

    > Favorite settings The model regularly used enable_sort=off and random_page_cost=1.1

    If random_page_cost wasn't set correctly for the default cases postgres's query planner can generate terrible plans (unless you're running on a spinning disk).

    That could easily explain the difference by itself.

    1. jneoioi · · focus · HN ↗

      [dead]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.