Re: Repeatable Read Isolation Level "transaction start time"

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Repeatable Read Isolation Level "transaction start time"
Date: 2024-09-25 20:22:31
Message-ID: CAKAnmmLDpwgqu071t_Q7Fq349dYAgQim1x46U1DCAiiTcUmU2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Sep 25, 2024 at 1:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Because we're not going to analyze the statement in the amount of depth
> needed to make that distinction before we crank up the
> transactional machinery. If it says SELECT, it gets a snapshot.
>

Ok, thanks. So to the original poster's point, perhaps the path with the
least side effects / best Principle of Least Surprise (POLS) support is to
start the transaction, and immediately call a "SELECT 1;" or perhaps better
still, a 'SELECT timeofday();'

Cheers,
Greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2024-09-25 20:36:20 Re: Repeatable Read Isolation Level "transaction start time"
Previous Message Ron Johnson 2024-09-25 17:56:51 Re: Repeatable Read Isolation Level "transaction start time"