Pipelining Redis Commands Does Not Make Them a Transaction
Pipelining cuts Redis request round trips, while MULTI/EXEC controls whether a group runs without another client interleaving. Choose by the state guarantee each operation needs.
Topic · 7 stories
7 stories tagged transactions on AI Tamer, newest first.
Pipelining cuts Redis request round trips, while MULTI/EXEC controls whether a group runs without another client interleaving. Choose by the state guarantee each operation needs.
A transaction can update two attached SQLite databases, but crash atomicity across both files depends on the main database and journal mode. Here is the boundary to check before relying on it.
SQLite busy timeout can wait for a lock to clear, but it may return SQLITE_BUSY immediately when waiting would preserve a transaction deadlock. Design retries around the whole transaction.
PostgreSQL prevents certain cross-row anomalies by aborting a Serializable transaction. Applications must replay the entire decision, including its reads.
A notification can wake a worker, while a committed table row records the work. Here is how to use both across startup and reconnects.
SQLite savepoints let you undo later work while keeping the surrounding transaction open. Here is how to use one and decide what to commit.
PostgreSQL does not reclaim sequence values after a transaction aborts. That is why generated IDs can have gaps, and why business counters need a separate design.