Re: PostgreSql: Canceled on conflict out to old pivot

Thanks guys for the valuable info. The key take away for me is clear: keep transactions short under all circumstances. Cheers, Eduard Am Fr., 1. Dez. 2023 um 01:31 Uhr schrieb Andres Freund : > Hi, > > On 2023-11-30 18:51:35 -0500, Tom Lane wrote: > > On what grounds do you assert that? Operati

Re: PostgreSql: Canceled on conflict out to old pivot

Hi, On 2023-11-30 18:51:35 -0500, Tom Lane wrote: > 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

Re: PostgreSql: Canceled on conflict out to old pivot

Heikki Linnakangas 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 aff

Re: PostgreSql: Canceled on conflict out to old pivot

On 30/11/2023 18:24, Wirch, Eduard wrote: > > The longest transaction that could occur is 1 min long. I hate to drill on this, but are you very sure about that? A transaction in a different database? Don't be sorry for that, drilling down is important. ;) It took me so long to reply because

Re: PostgreSql: Canceled on conflict out to old pivot

Thanks for the detailed answer, Heikki. > > The longest transaction that could occur is 1 min long. > I hate to drill on this, but are you very sure about that? A transaction in a different database? Don't be sorry for that, drilling down is important. ;) It took me so long to reply because I had

Re: PostgreSql: Canceled on conflict out to old pivot

On 28/11/2023 07:41, Wirch, Eduard wrote: ERROR: could not serialize access due to read/write dependencies among transactions   Detail: Reason code: Canceled on identification as a pivot, with conflict out to old committed transaction 61866959. There is a variation of the error: PSQLExceptio

Re: PostgreSql: Canceled on conflict out to old pivot

Hi, > On 28. Nov 2023, at 06:41, Wirch, Eduard wrote: > >  > > : > > ERROR: could not serialize access due to read/write dependencies among > transactions > Detail: Reason code: Canceled on identification as a pivot, with conflict > out to old committed transaction 61866959. > > There is