4 ms·
Postgres has "unlogged tables" for the not-exactly-persistent use case.
by ruricolist 13y ago
Postgres has "unlogged tables" for the not-exactly-persistent use case.
- saurik 13y agoAdditionally (as unclogged tables will cause total data loss on failure as opposed to just missing some updates) you can alternatively tune, per transaction, the durability of your changes: PostgreSQL lets you tune the durability of individual transactions using the synchronous_commit variable, letting you go entirely asynchronous (where you toss data at the database, it returns immediately, and will be saved to disk during the next ganged commit).