MIME-Version: 1.0
References: 
 <CAJk5AtZvkEdQsGLOEBAXuFv085End7H2T7SGkaEfTO1+QEARPw@mail.gmail.com>
 <2fd0442020d5b23609873f999b7d374875875689.camel@cybertec.at>
In-Reply-To: <2fd0442020d5b23609873f999b7d374875875689.camel@cybertec.at>
From: Raj <rajeshkumar.dba09@gmail.com>
Date: Mon, 13 Apr 2026 22:05:53 +0530
Message-ID: 
 <CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com>
Subject: Re: Slowness
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000043f65e064f5a143c"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJk5AtZ_7nKTLpVvduJCeVD%3DqMD%3DA9nVia%3DUmCWGo6JkbRMoRQ%40mail.gmail.com>
Precedence: bulk

--00000000000043f65e064f5a143c
Content-Type: text/plain; charset="UTF-8"

How long min duration statement is decided. Is it dba who decide how much
needs to be set?

On Mon, 13 Apr 2026, 18:32 Laurenz Albe, <laurenz.albe@cybertec.at> wrote:

> On Mon, 2026-04-13 at 18:25 +0530, Raj wrote:
> > When customer says they are facing slowness, what all wee need to check
> in
> > postgres db with 3 node patroni set up (sync between 1 and 2) - async
> with dr.
> >
> > We recently migrated from oracle to postgres..vacuum analyze is done.
> >
> > How to check this during the time slowness faced and also after couple
> of hrs of issue window.
> >
> > Should we start with pgstatstatements and logs or how is it. Help.me
> hight level what all I need to check
>
> You have to figure out *what exactly* is slow.  The customer has to tell
> you which
> statements are slow. The parameter "log_min_duratoin_statement" might help.
>
> Then you have to tune those statements.
>
> Yours,
> Laurenz Albe
>

--00000000000043f65e064f5a143c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">How long min duration statement is decided. Is it dba who=
 decide how much needs to be set?=C2=A0</div><br><div class=3D"gmail_quote =
gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 13 Apr=
 2026, 18:32 Laurenz Albe, &lt;<a href=3D"mailto:laurenz.albe@cybertec.at">=
laurenz.albe@cybertec.at</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">On Mon, 2026-04-13 at 18:25 +0530, Raj wrote:<br>
&gt; When customer says they are facing slowness, what all wee need to chec=
k in<br>
&gt; postgres db with 3 node patroni set up (sync between 1 and 2) - async =
with dr.<br>
&gt; <br>
&gt; We recently migrated from oracle to postgres..vacuum analyze is done.<=
br>
&gt; <br>
&gt; How to check this during the time slowness faced and also after couple=
 of hrs of issue window.<br>
&gt; <br>
&gt; Should we start with pgstatstatements and logs or how is it. Help.me h=
ight level what all I need to check<br>
<br>
You have to figure out *what exactly* is slow.=C2=A0 The customer has to te=
ll you which<br>
statements are slow. The parameter &quot;log_min_duratoin_statement&quot; m=
ight help.<br>
<br>
Then you have to tune those statements.<br>
<br>
Yours,<br>
Laurenz Albe<br>
</blockquote></div>

--00000000000043f65e064f5a143c--