you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (3 children)

Wouldn't that be an error due to serialisation failure if in postgres if you enabled serialisable isolation?

If you didn't, you could get anything, because unless I'm mistaken this is the typical example used to illustrate what goes wrong when you don't have full serialisable isolation.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 1 point 1 year ago (2 children)

    I believe both SERIALIZABLE and REPEATABLE READ isolation levels would raise an error for this example.

    And I looked this up: Postgres won't retry the transaction for you either. Though ultimately I think this a good default behavior.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    Why would repeatable read raise an error? I'm a little rusty but I thought it was only serialisable that could do, and that repeatable read simply ensured that the committed writes of transaction 2 would not be read in transaction 1, so it updating over the top of 2 is fine.

  • source
  • parent
  • hideshow 1 child comment