Re: Seeing high query planning time on Azure Postgres Single Server version 11.

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: hassan rafi <haassaan(dot)khann(at)gmail(dot)com>
Cc: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <rob(at)xzilla(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Seeing high query planning time on Azure Postgres Single Server version 11.
Date: 2024-03-15 00:26:21
Message-ID: CAApHDvqY-TWudNYdMhhnWE8RVYDSOZL-0TmBpV+P7ZhD_tLj2Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 15 Mar 2024 at 08:01, hassan rafi <haassaan(dot)khann(at)gmail(dot)com> wrote:
> We have migrated to postgres version 16.1, but still due to very high update activity on our DB, we are seeing elevated response times, though now the planning time is less.

> Buffers: shared hit=33359 read=6590 dirtied=9379

> Execution Time: 5049.131 ms

You could try "SET track_io_timing = 1;" to see how much of that time
is spent in reads.

David

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bandi, Venkataramana - Dell Team 2024-03-15 06:04:51 Query on Postgres SQL transaction
Previous Message David Rowley 2024-03-14 20:03:14 Re: select results on pg_class incomplete