[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: PostgreSql: Canceled on conflict out to old pivot
From:       Ron Johnson <ronljohnsonjr () gmail ! com>
Date:       2023-11-27 15:16:41
Message-ID: CANzqJaDES0Am_F-NJb_3UPpMpYE6wA-Tz-fuO0Bzw4U8ndTjzw () mail ! gmail ! com
[Download RAW message or body]

On Mon, Nov 27, 2023 at 2:17 AM Wirch, Eduard <eduard.w@smart-host.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?

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Mon, Nov 27, 2023 at 2:17 AM Wirch, Eduard &lt;<a \
href="mailto:eduard.w@smart-host.com">eduard.w@smart-host.com</a>&gt; \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi</div><div><br></div><div>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.</div></div></blockquote><div>  </div><div>Maybe I haven&#39;t had my coffee \
yet, but 100% of what?</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]