Repository navigation
Introduce a PostgreSQL based backend #731
Description
There have been multiple discussions around ValKey's durability guarantees and whether it's the right fit for Substrate. In #640 , Jet Chiang (@supreme-gg-gg) proposed a PostgreSQL alternative backend (see https://docs.google.com/document/d/12-ko_BFHcBo_nJkx9f4B7zMbiiWKC2saGhMhZG3aQ-s/edit?pli=1&tab=t.0 for a detailed benchmark).
This task is to introduce an alternative store PostgreSQL implementation, controlled by a binary flag.
Activity
mtaufen commentedon Aug 6, 2026
Why an "alternative" solution, if ValKey isn't the right fit to begin with? Seems like we should just switch to PostgreSQL.
Have we considered what to do for scale-out, after? What solutions are available for sharding PostgreSQL (anything like Vitess?)?
ateapi: Support Postgres as alternative persistence backend (#640)
Harden PostgreSQL concurrency, integrity, and error handling (#1023)
BenTheElder commentedon Aug 26, 2026
This is done. And it is now the default / only.