From: Andreas Kretschmer <andreas@a-kretschmer.de>
To: pgsql-general@lists.postgresql.org
Subject: Re: How to investigate deadlocks
Date: Mon, 2 Oct 2023 13:39:00 +0200
Message-ID: <20c3aadc-e589-c601-c2a7-0ca89a7cec66@a-kretschmer.de> (raw)
In-Reply-To: <ZRqpLukFBYbDBnrG@pureos>
References: <ZRqpLukFBYbDBnrG@pureos>
Am 02.10.23 um 13:27 schrieb Matthias Apitz:
> Hello,
>
> One of our clients running our LMS on top of PostgreSQL 13.1 created a
> ticket with these messages:
>
> 2023-09-30 16:50:50.951 CEST [18117] ERROR: deadlock detected
> 2023-09-30 16:50:50.951 CEST [18117] DETAIL: Process 18117 waits for ShareLock on transaction 150396154; blocked by process 18187.
> Process 18187 waits for ShareLock on transaction 150396155; blocked by process 18117.
> Process 18117: fetch hc_d03geb
> Process 18187: fetch hc_d02ben
> 2023-09-30 16:50:50.951 CEST [18117] HINT: See server log for query details.
> 2023-09-30 16:50:50.951 CEST [18117] CONTEXT: while locking tuple (38,57) in relation "d03geb"
> 2023-09-30 16:50:50.951 CEST [18117] STATEMENT: fetch hc_d03geb
>
> The shown PIDs for sure are the ones of the Pos backend proc (on Linux).
> Is there any chance to investigate it further?
please also check
https://www.cybertec-postgresql.com/en/postgresql-understanding-deadlocks/
Andreas
--
Andreas Kretschmer
Technical Account Manager (TAM)
www.enterprisedb.com
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: andreas@a-kretschmer.de
Subject: Re: How to investigate deadlocks
In-Reply-To: <20c3aadc-e589-c601-c2a7-0ca89a7cec66@a-kretschmer.de>
References: <ZRqpLukFBYbDBnrG@pureos> <20c3aadc-e589-c601-c2a7-0ca89a7cec66@a-kretschmer.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox