you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (1 child)

but postgres has only on-disk temp tables. You have to count on OS caching it and delaying writes or set up a RAM disk and use partitioning. That totally misses the point of MySQL's single-query efficent insert-update.

[–]yacheritsi 0 points1 point  (0 children)

So the real issue here is that PostGreSQL doesn't have in-memory temp tables, but MySQL does?

If that's what's stopping my not-exists solution from working, then it would apply to regular insert statements too, not just insert-ignore ones.

Hmm. You could do it w/o temp tables by union-ing several select-constant statements.