public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Heikki Linnakangas <[email protected]>
Cc: Wirch, Eduard <[email protected]>
Cc: [email protected]
Subject: Re: PostgreSql: Canceled on conflict out to old pivot
Date: Thu, 30 Nov 2023 18:51:35 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAPX+m-hdbj4b1Ufcpx+YAGj8BLF91gdi6zr0Pc3NKZTBDtKUrQ@mail.gmail.com>
	<[email protected]>
	<CAPX+m-jF52dHkve0et0WAScC2JkELChdmxVUNbTCrDM0oq903Q@mail.gmail.com>
	<[email protected]>

Heikki Linnakangas <[email protected]> writes:
> On 30/11/2023 18:24, Wirch, Eduard wrote:
>> My understanding of serializable isolation is that only transactions
>> which can somehow affect each other can conflict. It should be clear
>> for PostgreSql, that transactions belonging to different databases
>> cannot affect each other. Why do they cause serializable conflicts?

On what grounds do you assert that?  Operations on shared catalogs
are visible across databases.  Admittedly they can't be written by
ordinary DML, and I'm not sure that we make any promises about DDL
writes honoring serializability.  But I'm unwilling to add
"optimizations" that assume that that will never happen.

			regards, tom lane

view thread (5+ 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], [email protected], [email protected]
  Subject: Re: PostgreSql: Canceled on conflict out to old pivot
  In-Reply-To: <[email protected]>

* 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