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
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
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
we don't preserve it today.
If you want something visual, I prepared a SO question with similar
content like this mail, but added an image of the tx flow:
https://stackoverflow.com/questions/77544821/postgresql-canceled-on-conflict-out-to-old-pivot <https://stackoverflow.com/questions/77
/questions/77544821/postgresql-canceled-on-conflict-out-to-old-pivot
Cheers,
Eduard
Am Di., 28. Nov. 2023 um 09:53 Uhr schrieb Heikki Linnakangas <
hlinn...@iki.fi>:
> On 28/11/2023 07:41, Wirch, Eduard wrote:
> > ERROR: could not serialize access due to read/write dependencies am
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
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
Hi
I posted this question already on pgsql-general, but it got no answers.
Maybe the topic is too technical? So I'm trying it here. Maybe a SSI
specialist is here on the list.
We have a PostgreSql 15 server serving around 30 databases, one schema each
with the same layout. Each database is used b
