Boosting Postgres Insert Performance by 50% with Unnest
timescale.comHi HN! If you're interested in PostgreSQL or database performance here's a short benchmark I did looking into the seemingly magical performance gain you can get by INSERTing unnested arrays rather than VALUES tuples in Postgres.
Let me know if you have any questions or suggestions for next articles.
Interesting, is there a reason why Postgres wouldn't just apply the shared query planning to INSERT...VALUES as well, it seems like almost a no-brainer to speed up all queries. Or is this more related to how the parser works with the values?