MIME-Version: 1.0
References: 
 <CAJk5AtZvkEdQsGLOEBAXuFv085End7H2T7SGkaEfTO1+QEARPw@mail.gmail.com>
 <2fd0442020d5b23609873f999b7d374875875689.camel@cybertec.at>
 <CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com>
 <efb70f15e61eaa95bcfa6039f6dd086481fc4bdb.camel@cybertec.at>
In-Reply-To: <efb70f15e61eaa95bcfa6039f6dd086481fc4bdb.camel@cybertec.at>
From: Raj <rajeshkumar.dba09@gmail.com>
Date: Mon, 13 Apr 2026 23:13:41 +0530
Message-ID: 
 <CAJk5AtZ1-N4hs=6D1NtnNNt116e9kjEhpFdakrkJUJtgaL_xKQ@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="000000000000cb7fb3064f5b06f9"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJk5AtZ1-N4hs%3D6D1NtnNNt116e9kjEhpFdakrkJUJtgaL_xKQ%40mail.gmail.com>
Precedence: bulk

--000000000000cb7fb3064f5b06f9
Content-Type: text/plain; charset="UTF-8"

Ok great. If I start with normal health check top, free -h, patronictl
list, and all status of components such as etcd, haproxy etcd pgnouncer ,
then stat user tables, pgstatactivity, pgstatstatements and error log.
Apart from this, what dba should do?

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

> On Mon, 2026-04-13 at 22:05 +0530, Raj wrote:
> > 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.
> >
> > How long min duration statement is decided. Is it dba who decide how
> much needs to be set?
>
> Sorry, I made a typo.  It is a database parameter and called
> "log_min_duration_statement".
>
> Your questions seem to indicate that you have almost no knowledge about
> PostgreSQL.
> Without database knowledge, it is impossible to find slow statements, let
> alone tune
> them.  Perhaps you should spend some time with the PostgreSQL
> documentation or hire
> a consultant.
>
> Yours,
> Laurenz Albe
>

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

<div dir=3D"auto"><div>Ok great. If I start with normal health check top, f=
ree -h, patronictl list, and all status of components such as etcd, haproxy=
 etcd pgnouncer , then stat user tables, pgstatactivity, pgstatstatements a=
nd error log. Apart from this, what dba should do?<br><br><div class=3D"gma=
il_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mo=
n, 13 Apr 2026, 22:45 Laurenz Albe, &lt;<a href=3D"mailto:laurenz.albe@cybe=
rtec.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;padd=
ing-left:1ex">On Mon, 2026-04-13 at 22:05 +0530, Raj wrote:<br>
&gt; On Mon, 13 Apr 2026, 18:32 Laurenz Albe, &lt;<a href=3D"mailto:laurenz=
.albe@cybertec.at" target=3D"_blank" rel=3D"noreferrer">laurenz.albe@cybert=
ec.at</a>&gt; wrote:<br>
&gt; &gt; On Mon, 2026-04-13 at 18:25 +0530, Raj wrote:<br>
&gt; &gt; &gt; When customer says they are facing slowness, what all wee ne=
ed to check in<br>
&gt; &gt; &gt; postgres db with 3 node patroni set up (sync between 1 and 2=
) - async with dr.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; We recently migrated from oracle to postgres..vacuum analyze=
 is done.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; How to check this during the time slowness faced and also af=
ter couple of hrs of issue window.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Should we start with pgstatstatements and logs or how is it.=
 Help.me hight level what all I need to check<br>
&gt; &gt; <br>
&gt; &gt; You have to figure out *what exactly* is slow.=C2=A0 The customer=
 has to tell you which<br>
&gt; &gt; statements are slow. The parameter &quot;log_min_duratoin_stateme=
nt&quot; might help.<br>
&gt; &gt; <br>
&gt; &gt; Then you have to tune those statements.<br>
&gt;<br>
&gt; How long min duration statement is decided. Is it dba who decide how m=
uch needs to be set?<br>
<br>
Sorry, I made a typo.=C2=A0 It is a database parameter and called &quot;log=
_min_duration_statement&quot;.<br>
<br>
Your questions seem to indicate that you have almost no knowledge about Pos=
tgreSQL.<br>
Without database knowledge, it is impossible to find slow statements, let a=
lone tune<br>
them.=C2=A0 Perhaps you should spend some time with the PostgreSQL document=
ation or hire<br>
a consultant.<br>
<br>
Yours,<br>
Laurenz Albe<br>
</blockquote></div></div></div>

--000000000000cb7fb3064f5b06f9--