MIME-Version: 1.0
References: 
 <CAJk5AtZvkEdQsGLOEBAXuFv085End7H2T7SGkaEfTO1+QEARPw@mail.gmail.com>
 <2fd0442020d5b23609873f999b7d374875875689.camel@cybertec.at>
 <CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com>
In-Reply-To: 
 <CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Mon, 13 Apr 2026 13:11:06 -0400
Message-ID: 
 <CANzqJaC=321==QbieX7soJzqycpFXWyFURkquWdk0+MUvSe=Lw@mail.gmail.com>
Subject: Re: Slowness
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000258093064f5a9266"
Archived-At: 
 <https://www.postgresql.org/message-id/CANzqJaC%3D321%3D%3DQbieX7soJzqycpFXWyFURkquWdk0%2BMUvSe%3DLw%40mail.gmail.com>
Precedence: bulk

--000000000000258093064f5a9266
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

"All the stakeholders" decide the threshold.  For example, if *they*
complain about queries taking more than 2 seconds, you obviously shouldn't
set log_min_duratoin_statement to 5 seconds.

If they don't know, are too clueless to know, or it's a mixed OLTP &
reporting database, pick a reasonable value and go from there.

You can always change it later...

On Mon, Apr 13, 2026 at 12:36=E2=80=AFPM Raj <rajeshkumar.dba09@gmail.com> =
wrote:

> 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 chec=
k
>> 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
>>
>

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

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

<div dir=3D"ltr"><div>&quot;All the stakeholders&quot; decide the threshold=
.=C2=A0 For example, if <i>they</i> complain about queries taking more than=
 2 seconds, you obviously shouldn&#39;t set log_min_duratoin_statement to 5=
 seconds.</div><div><br></div><div>If they don&#39;t know, are too clueless=
 to know, or it&#39;s a mixed OLTP &amp; reporting database, pick a reasona=
ble value and go from there.</div><div><br></div><div>You can always change=
 it later...=C2=A0</div><br><div class=3D"gmail_quote gmail_quote_container=
"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Apr 13, 2026 at 12:36=E2=80=
=AFPM Raj &lt;<a href=3D"mailto:rajeshkumar.dba09@gmail.com">rajeshkumar.db=
a09@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><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"><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" target=3D=
"_blank">laurenz.albe@cybertec.at</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On Mon, 2026-04-13 at 18:25 +0530, Raj wro=
te:<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>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div=
>Don&#39;t boil me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobs=
ter!</div></div></div></div></div></div>

--000000000000258093064f5a9266--