Re: PostgreSql: Canceled on conflict out to old pivot

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSql: Canceled on conflict out to old pivot
Date: 2023-11-27 15:16:41
Message-ID: CANzqJaDES0Am_F-NJb_3UPpMpYE6wA-Tz-fuO0Bzw4U8ndTjzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 27, 2023 at 2:17 AM Wirch, Eduard <eduard(dot)w(at)smart-host(dot)com>
wrote:

> Hi
>
> We have a PostgreSql 15 server serving around 30 databases, one schema
> each with the same layout. Each database is used by one application
> instance. The application consistently uses transactions with isolation
> level serializable to access the database, optimizing by using explicit
> read only transactions, where applicable. Once the server reaches 100% we
> get an increased amount of serialize conflict errors.
>

Maybe I haven't had my coffee yet, but 100% of what?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2023-11-27 15:26:43 Re: Emitting JSON to file using COPY TO
Previous Message Tom Lane 2023-11-27 14:56:22 Re: Emitting JSON to file using COPY TO