3 ms·
Once again. PostgresSQL does not have in-memory tables. So: a) Writes will be happening on a slow, highly contentious disk. b) You have no guarantees that the
by threeseed 2y ago
Once again. PostgresSQL does not have in-memory tables. So:
a) Writes will be happening on a slow, highly contentious disk.
b) You have no guarantees that the data will be in-memory.
Both of which make it a poor solution for use cases such as locking.
- natmaka 2y agoAs pointed out by blackenedgem above: PostgreSQL has tablespaces, and one may simply declare tables which should stay in RAM in a tablespace built upon a tmpfs with enough reserved RAM to store them all. There is a only small associated burden (restoring the tablespace while starting PG).