| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: High latency and profiling |
| Date: | 2025-10-09 20:54:56 |
| Message-ID: | 0c57f712-24c7-4f50-8d5f-7a1f42bff711@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
>>
>>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-10-09 21:18:03 | Re: Clarification on Role Access Rights to Table Indexes |
| Previous Message | Laurenz Albe | 2025-10-09 19:21:19 | Re: High latency and profiling |