Serializable description seems misleading?

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: ajantha_perera(at)yahoo(dot)com
Subject: Serializable description seems misleading?
Date: 2019-12-10 21:49:54
Message-ID: 157601459454.18137.13976433380958895558@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/12/transaction-iso.html
Description:

Let's say I have two transactions running in Serializable isolation:
T1: Reads a row
T2: Reads the same row
T1: Updates the row
T1: Commits
T2: Commits

You will not get an error on the second commit. These appear to fit the
description of concurrent transactions, and running one before the other
would give different results in the reading of the row by T2, depending on
which transaction was executed first. So how does this square with the docs
that state "it monitors for conditions which could make execution of a
concurrent set of serializable transactions behave in a manner inconsistent
with all possible serial (one at a time) executions".

This seems quite misleading, but I understand there may just be an aspect of
this that I am not understanding.

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Yasuhiro Horimoto 2019-12-11 00:40:26 Re: I suggest improving install steps for CentOS 8
Previous Message Magnus Hagander 2019-12-10 20:00:06 Re: I suggest improving install steps for CentOS 8