Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1stYxp-00HORK-LE for pgsql-general@arkaria.postgresql.org; Wed, 25 Sep 2024 20:50:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1stYxo-00E55w-7W for pgsql-general@arkaria.postgresql.org; Wed, 25 Sep 2024 20:50:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1stYxn-00E55o-Sq for pgsql-general@lists.postgresql.org; Wed, 25 Sep 2024 20:50:19 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1stYxh-00131v-Dg for pgsql-general@lists.postgresql.org; Wed, 25 Sep 2024 20:50:18 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2f74e613a10so4999981fa.1 for ; Wed, 25 Sep 2024 13:50:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727297411; x=1727902211; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iP/DZxLw1ran/kkwsXfdtm1PHGTBBJzAXl5UHVXH7Bs=; b=fk0tW4TKiLmhHkh2S6X4q/yhrepjCEDaf38gG0MV5yUjxXpGWxU4A8TQwcV5rQSvoQ Ngox0J1cENkUJU6YiJHfW5BS0oTgSsx+5k615QocmxEXZcmxd0AtKcxy72xgSvKXvlEM u1803IkJ/qcI8YAhwCUPWy5lKmRrQZNOiP8f84N8FgJPefQkx8xC6ikSjiQgHlDvRAAK gW+5bGQ8775HDhy3yS3eerIdYKiPTveAKz4RPRIfnHZ6Y6rOWCrRtfEvCadt0DgZCvQB rQ5CqmYklTH+B8ED2fDsrcxFtn0E/dF/AcmzQbpw3iwIavQmSrgBhMARC3VWX1odE6Ps XYBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727297411; x=1727902211; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iP/DZxLw1ran/kkwsXfdtm1PHGTBBJzAXl5UHVXH7Bs=; b=RNk4Afqvdg4aE54aH6jX5CTua2VnhKfBLWe0nwj6Z7gypzRIRiJK4kRcNqX8a/tCpK n7/V1i58sA04nVC1dpTQzUTxv9A3pUhDHTSooF3OwfHqBCtAdRkr+7tW/gZMaSdABz9e nX8hMcFeEjA/XpyGWLri/87gPCusRi9tLV5AxNXnzkWjb13+ATvuDsTgKG0DUxKBLXvD ut/GCMu/nos2iLTqu0JqQoI44etdGF8Ldfq7OnHBfa3Ny4O/wkw+aXSH3MXKhWlwrO5E xXf9WmM/nLYFIOaQKEv6Blx78U/eiCBgQmoA1Ugvtk3zs3BlrhUR/hJ4vdBmk4siZQ1f zjxQ== X-Gm-Message-State: AOJu0YwhQjn0KK9NEpffbHdOLNPDg4p6uIAeVsT52elC/shrHTIciEUF GVyqPDsiMxXny2vyBeC/MkI9t/A8Aou+uvBUG0no7ow++jo7+DavnaeYia4ZGhfag4WyWLFxwej k5zb2BNJuFgMUDsy29PyhAVBW4zA= X-Google-Smtp-Source: AGHT+IEVKnoEw51rK4yk3TEcZsEUGHHCFf7FSgD12h0lQrUTbwQocJ0i8/cz8lkopePsV0WXAV8bMARVbIfFf2QcTbk= X-Received: by 2002:a2e:a9a9:0:b0:2ef:1b1b:7f42 with SMTP id 38308e7fff4ca-2f91ca351ccmr38486701fa.36.1727297411308; Wed, 25 Sep 2024 13:50:11 -0700 (PDT) MIME-Version: 1.0 References: <9CEBFAC7-4372-4FF0-8124-FFFE834B03C6@gmail.com> <3346993.1727188126@sss.pgh.pa.us> <28109.1727286817@sss.pgh.pa.us> In-Reply-To: From: Greg Sabino Mullane Date: Wed, 25 Sep 2024 16:49:34 -0400 Message-ID: Subject: Re: Repeatable Read Isolation Level "transaction start time" To: Ron Johnson Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000009f69670622f7c444" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009f69670622f7c444 Content-Type: text/plain; charset="UTF-8" > > Since transactions should be "as short as possible, without being too >> short", how much time is there between when you run "BEGIN;" and the first >> "work statement"? >> > I don't know that it really matters. For something automated, it would be a few milliseconds. Either way, I'm sure most people/apps already think of the initial 'BEGIN ...' as the start of the transaction, and act accordingly. Maybe long-term something like BEGIN ISOLATION MODE REPEATABLE READ SNAPSHOT NOW; could be useful. Cheers, Greg --0000000000009f69670622f7c444 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Since transactions should be "as short as possible, without bei= ng too short", how much time is there between when you run "BEGIN= ;" and the first "work statement"?
<= /div>

I don't know that it really= matters. For something automated, it would be a few milliseconds. Either w= ay, I'm sure most people/apps already think of the initial 'BEGIN .= ..' as the=C2=A0start of the transaction, and act accordingly.

Maybe long-term something like

BE= GIN=C2=A0 =C2=A0ISOLATION MODE REPEATABLE READ=C2=A0 =C2=A0SNAPSHOT NOW;

could be useful.

Cheers,
Greg


--0000000000009f69670622f7c444--