public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ron Johnson <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Repeatable Read Isolation Level "transaction start time"
Date: Tue, 24 Sep 2024 08:59:01 -0400
Message-ID: <CANzqJaC0Puj0WnnjQ2K2qy1MQJY4O8QP5uJbNoqeQrhfdgJ8Xg@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwYvh02jtAAmybAPGC00k-AWiOqm3vT2Aj3m8dKLO+fugg@mail.gmail.com>
References: <[email protected]>
	<CAKFQuwYvh02jtAAmybAPGC00k-AWiOqm3vT2Aj3m8dKLO+fugg@mail.gmail.com>

On Tue, Sep 24, 2024 at 8:29 AM David G. Johnston <
[email protected]> wrote:

> On Monday, September 23, 2024, Wizard Brony <[email protected]> wrote:
>
>>
>> https://www.postgresql.org/docs/16/transaction-iso.html#XACT-REPEATABLE-READ
>>
>> The PostgreSQL documentation for the Repeatable Read Isolation Level
>> states the following:
>>
>> “UPDATE, DELETE, MERGE, SELECT FOR UPDATE, and SELECT FOR SHARE commands
>> behave the same as SELECT in terms of searching for target rows: they will
>> only find target rows that were committed as of the transaction start time.”
>>
>> What is defined as the "transaction start time?" When I first read the
>> statement, I interpreted it as the start of the transaction:
>>
>> BEGIN;
>> SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
>>
>> But in my testing, I find that according to that statement, the
>> transaction start time is actually "the start of the first
>> non-transaction-control statement in the transaction" (as mentioned earlier
>> in the section). Is my conclusion correct, or am I misunderstanding the
>> documentation?
>>
>>
> Probably, since indeed the transaction cannot start at begin because once
> it does start it cannot be modified.
>

Huh?

-- 
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> crustacean!

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Repeatable Read Isolation Level "transaction start time"
  In-Reply-To: <CANzqJaC0Puj0WnnjQ2K2qy1MQJY4O8QP5uJbNoqeQrhfdgJ8Xg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox