Skeptical about replacing Redis with a table serialized to disk. The point of Redis is that it is in memory and you can smash it with hot path queries while taking a lot of load off the backing DB. Also that design requires a cron which means the table could fill disk between key purges.

▲

dry_soup 7 hours ago | parent [-]

From the article, using UNLOGGED tables puts them in memory, not on disk

	▲	samuelknight 6 hours ago \| parent [-]
		I the article is wrong. UNLOGGED means it isn't written to WAL which means recovery and rollback guarantees won't work since the transaction can finish before the page can be synchronized on disk. The table loses integrity as a trade off for a faster write. https://www.postgresql.org/docs/current/sql-createtable.html...