5 ms·
Parent is talking about temporary tables. Those are normally only live for the duration of a transaction (well, session, but in practice if you're using tempora
by barrkel 5y ago
Parent is talking about temporary tables. Those are normally only live for the duration of a transaction (well, session, but in practice if you're using temporary tables across multiple transactions you have a logical application-level transaction which needs to be able to handle failure part-way through). After your transaction the writes to non-temporary tables should be persistent.
Postgres temp tables on ramdisk are a problem for a different reason, the WAL, as pointed to by a sibling comment.
- natmaka 5y ago> Postgres temp tables on ramdisk are a problem for a different reason, the WAL, as pointed to by a sibling comment TEMPORARY tables are UNLOGGED, and therefore they aren't WALed
- raffraffraff 5y agoGotcha, somehow missed that. Yeah, tmp tables on disks are painful and I've made the same optimization on MySQL whenever it wasn't possible to eliminate the need to tmp tables by refactoring SQL.