/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

hakibenita.com
| | boringsql.com
6.1 parsecs away

Travel
| | Two concurrent sessions, same page, different answers. An interactive tour of xmin, xmax, snapshots, and the visibility rules that decide what PostgreSQL lets you see.
| | johnjr.dev
6.9 parsecs away

Travel
| | When we study transactions in relational databases, one of the first things we learn are the guarantees that a transaction must provide. ACID(Atomicity, Consistency, Isolation, Durability) are the properties that we desire. Here, I will discuss the Isolation level in more detail and show that atomicity alone is not enough when handling concurrency. One classic example of the importance of atomicity is moving money between accounts. So, imagine that we have two accounts and we would like to transfer the total amount from one account to another one. In a relational database, what we need to do is three steps:
| | pgdba.org
3.6 parsecs away

Travel
| | [AI summary] This technical article explains the Multi-Version Concurrency Control (MVCC) and transaction isolation levels in PostgreSQL, including how XIDs work and common concurrency issues.
| | blog.dancrisan.com
13.4 parsecs away

Travel
| In real life, users access a database concurrently. Database access is done through transactions. What is a transaction? a unit of work that has to be treated as "a whole" it has to happen in full or not at all A real life example of a transaction... | Dan Crisan | Techie, Blogger, Diversity Advocate and A Little Bit More . This is my technical blog (: