k_yrs_go is a database server for Yjs documents. It works on top of Postgres and Redis. k_yrs_go uses binary redis queues as I/O buffers for YJS document updates, and uses the following PG table to store the updates:
CREATE TABLE IF NOT EXISTS k_yrs_go_yupdates_store (
id TEXT PRIMARY KEY,
doc_id TEXT NOT NULL,
data BYTEA NOT NULL
);
CREATE INDEX IF NOT EXISTS k_yrs_go_yupdates_store_doc_id_idx ON k_yrs_go_yupdates_store (doc_id);
Rows in k_yrs_go_yupdates_store undergo compaction when fetching the state for a document if the number of rows of updates for the doc_id are > 100 in count. Compaction happens in a serializable transaction, and the combined-yupdate is inserted in the table only when the number of deleted yupdates is equal to what was fetched from the db.
Even the Reads and Writes happen in serializable transactions. From what all I have read about databases, Reads, Writes, and Compactions in k_yrs_go should be consistent with each other.
Max document size supported is 1 GB.