Database Transaction Isolation
Discussions center on using transactions, MVCC, snapshot isolation, and ACID properties (especially isolation) in databases like Postgres to manage concurrency and prevent race conditions.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Basically, the correct way is to use transactions. Use a transactional database because it supports MVCC.
Im sorry, maybe im just inexperienced here, but doesnt what you're describing violate the isolation part of ACID? https://en.wikipedia.org/wiki/Isolation_(database_systems)
Seems like if you tried to use transactions, you'd have the same problem?
What's being discussed is MVCC, or multiversion concurrency controlhttps://en.wikipedia.org/wiki/Multiversion_concurrency_contr...
Yes, be aware of the transactional capabilities of your database. Some ACID databases in their default configuration don't provide all transactional guarantees!
Sounds like https://en.wikipedia.org/wiki/Snapshot_isolation.
IDK, what about indexes? what about atomic transactions which add/update/delete rows to/from/from multiple tables?
Guessing you don't need atomic DB transactions in that case.
well Postgres does not need to do anything you can start a transaction and you have exactly that.
Doesn't your RDBMS support transactions?