| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Roberto Nunnari <robi(at)nunnari(dot)ch>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: High latency and profiling |
| Date: | 2025-10-09 19:21:19 |
| Message-ID: | 938cf470050825d031f624b57f6ca46949304691.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
> Could somebody help me understand what is causing the growing latency?
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 | Rob Sargent | 2025-10-09 20:54:56 | Re: High latency and profiling |
| Previous Message | Laurenz Albe | 2025-10-09 19:12:07 | Re: Are compression requirements needed when building only libraries? |