Search Postgresql Archives

Re: Serializable read only deferrable- implications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Serializable read only deferrable- implications
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Date: Tue, 8 Mar 2022 09:16:37 -0700
Cc: PostgreSQL General <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <beefe50e38101af2b183fb7e04ddd252169b6e3e.camel@cybertec.at>
References: <CAHOFxGrrab_d3sOWy-jZWYVf=teP+u_c2KXYaZeFTqwhOrVS=A@mail.gmail.com> <beefe50e38101af2b183fb7e04ddd252169b6e3e.camel@cybertec.at>

A transaction started with the first statement will not take any SI locks, nor
will it ever receive a serialization error.

What is the meaning of SI? Anything you are aware of in source code or a blog post that discusses this?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Serializable read only deferrable- implications
  - From: Tom Lane

References:
- Serializable read only deferrable- implications
  - From: Michael Lewis
- Re: Serializable read only deferrable- implications
  - From: Laurenz Albe

Prev by Date: Re: Serializable read only deferrable- implications
Next by Date: Re: Serializable read only deferrable- implications
Previous by thread: Re: Serializable read only deferrable- implications
Next by thread: Re: Serializable read only deferrable- implications
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux