From: | Nikolay Samokhvalov <nik(at)postgres(dot)ai> |
---|---|
To: | Eric Schwarzenbach <subscriber(at)blackbrook(dot)org> |
Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: can a blocked transaction affect the performance of one that is blocking it? |
Date: | 2024-12-09 23:10:32 |
Message-ID: | CAM527d_JP20hZ9bLKWUmMXx_bQms4B=W4321HApfcQ98cx_1HA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Dec 9, 2024 at 13:16 Eric Schwarzenbach <subscriber(at)blackbrook(dot)org>
wrote:
> Hi,
>
> Could one transaction (one that should be relatively simple and short)
> cause another complex, long running transaction (involving INSERTS, on a
> table the first transaction may be reading from) to take many orders of
> magnitude longer than it would normally? (short of competing for system
> resources, like CPU time etc, of course)
>
> I don't believe my scenario involved a deadlock but I expect my short
> transaction was probably blocked by my long one. Does it make any sense
> that this could very significantly affect the performance of the
> non-blocked transaction?
>
> Thanks,
>
> Eric
Have you tried wait event analysis (looking at wait_event_type, wait_event,
state, query samples from pg_stat_activity)?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2024-12-09 23:20:38 | Re: proposal: schema variables |
Previous Message | Eric Schwarzenbach | 2024-12-09 18:42:30 | can a blocked transaction affect the performance of one that is blocking it? |