Message-ID: <efb70f15e61eaa95bcfa6039f6dd086481fc4bdb.camel@cybertec.at>
Subject: Re: Slowness
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Raj <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Date: Mon, 13 Apr 2026 19:15:26 +0200
In-Reply-To: 
 <CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com>
References: 
	<CAJk5AtZvkEdQsGLOEBAXuFv085End7H2T7SGkaEfTO1+QEARPw@mail.gmail.com>
	 <2fd0442020d5b23609873f999b7d374875875689.camel@cybertec.at>
	 <CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/efb70f15e61eaa95bcfa6039f6dd086481fc4bdb.camel%40cybertec.at>
Precedence: bulk

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 che=
ck in
> > > postgres db with 3 node patroni set up (sync between 1 and 2) - async=
 with dr.
> > >=20
> > > We recently migrated from oracle to postgres..vacuum analyze is done.
> > >=20
> > > How to check this during the time slowness faced and also after coupl=
e of hrs of issue window.
> > >=20
> > > Should we start with pgstatstatements and logs or how is it. Help.me =
hight level what all I need to check
> >=20
> > You have to figure out *what exactly* is slow.=C2=A0 The customer has t=
o tell you which
> > statements are slow. The parameter "log_min_duratoin_statement" might h=
elp.
> >=20
> > 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_durat=
ion_statement".

Your questions seem to indicate that you have almost no knowledge about Pos=
tgreSQL.
Without database knowledge, it is impossible to find slow statements, let a=
lone tune
them.  Perhaps you should spend some time with the PostgreSQL documentation=
 or hire
a consultant.

Yours,
Laurenz Albe