New answers tagged

0

Database server RAM is always scarce, so it is best reserved for caching stuff that is needed often by many clients, like most accessed rows etc. Postgres doesn't support RAM-only tables. But if it did, if you had lots of clients creating RAM tables, you'd have to be very careful not to use too much RAM on the server for data that only client uses, while at ...


2

You might be missing the obvious candidate: a TEMPORARY TABLE. It lives in memory if enough RAM has been allocated with the temp_buffers setting. Only the current session can see it, no WAL is written for it (which is the main reason why it's faster) and it is dropped at the end of the session automatically. If it must live past the current session, consider ...


2

Doing smaller transactions and keeping connections not open (Open Transactions) for long time will probably do the job. And: The undo log is usually part of the physical system tablespace, but from MariaDB 10.0, the innodb_undo_directory and innodb_undo_tablespaces system variables can be used to split into different tablespaces and store in a different ...


Top 50 recent answers are included