Temp tables in Postgres don't scale
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
PostgresAI's Nikolay Samokhvalov measured CREATE TEMP TABLE run in every transaction on Postgres 18 (16 vCPU): 3783 TPS, against 17866 for a table kept per session and 86997 for a CTE. Each create and drop touches 31 catalog rows. With 5000 idle sessions and a 500 TPS target, temp-table DDL reached 127 and 249 TPS in two runs, as the shared invalidation queue became the limit. The figures come from the author's own experiments and could not be independently checked.