Re: High latency and profiling - Mailing list pgsql-general

From Rob Sargent
Subject Re: High latency and profiling
Date
Msg-id 0c57f712-24c7-4f50-8d5f-7a1f42bff711@gmail.com
Whole thread Raw
In response to Re: High latency and profiling  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general

On 10/9/25 13:21, Laurenz Albe wrote:
> On Thu, 2025-10-09 at 19:25 +0200, Roberto Nunnari wrote:
>> I was notified about high latency on one of our PostgreSQL clusters.
>> This latency is observed from the application and has been increasing.
>> There is no indication about the exact database as the application uses
>> several DBs, but the largest and most used is 'mydb'.
>>
>> Developers report that their software is already optimized and database
>> size is not a problem. They suggest the issue might be inside PostgreSQL
>> itself.
> That may be true, but it need not be true.  The developers' statement
> sounds a bit overconfident.
Thankfully I checked before sending very similar remarks as Laurenz's 
below.  I find OP's pair of sentences (borderline) self-contradictory.


>> For that, you have to identify the statements that run longer than they
>> should.  Then examine them with EXPLAIN (ANALYZE, BUFFERS), figure out what
>> makes them slow and improve them.
>>
>> Yours,
>> Laurenz Albe
>>
>>
>>




pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: High latency and profiling
Next
From: "Vu Le (JData - HN)"
Date:
Subject: Upgrade & Rollback plan: My customer requests rollback via old-version standby (13 ↔ 17) — need community advice