public inbox for [email protected]  

help / color / mirror / Atom feed

From: Justin <[email protected]>
To: Alec Cozens <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: LWLock SerializableFinishedList
Date: Tue, 9 Sep 2025 15:42:30 -0400
Message-ID: <CALL-XeNqwTVJpjadqqL_ws965C_1EuP0wxrEu78AFTK+Tx5rRA@mail.gmail.com> (raw)
In-Reply-To: <LO2P123MB1711F8A621404614ED676F7DCD0CA@LO2P123MB1711.GBRP123.PROD.OUTLOOK.COM>
References: <LO2P123MB17113181847230A9D67C8602CD03A@LO2P123MB1711.GBRP123.PROD.OUTLOOK.COM>
	<CALL-XeMUhHnqZx083rWx14xX2XjqBeq7h94TOfXBtoaSGzhxWg@mail.gmail.com>
	<LO2P123MB1711F8A621404614ED676F7DCD0CA@LO2P123MB1711.GBRP123.PROD.OUTLOOK.COM>

Also reviewing if we really need SERIALIZED and could instead use READ
COMMITTED. Would that be likely to mitigate against this happening?

PostgreSQL can NOT  go below READ COMMITTED in transaction isolation
levels.  Read Committed is the default mode for all transactions in
PostgreSQL

https://www.postgresql.org/docs/17/transaction-iso.html

Unless there is a very specific need for serializing transactions such as
financial calculations or updating and calculating  the remaining number of
tickets to sell for a concert,  Serialization adds a lot of overhead for
not much gain..

thanks

view thread (2+ messages)

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: LWLock SerializableFinishedList
  In-Reply-To: <CALL-XeNqwTVJpjadqqL_ws965C_1EuP0wxrEu78AFTK+Tx5rRA@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