Message-ID: <2fd0442020d5b23609873f999b7d374875875689.camel@cybertec.at>
Subject: Re: Slowness
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Raj <rajeshkumar.dba09@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Mon, 13 Apr 2026 15:02:26 +0200
In-Reply-To: 
 <CAJk5AtZvkEdQsGLOEBAXuFv085End7H2T7SGkaEfTO1+QEARPw@mail.gmail.com>
References: 
	<CAJk5AtZvkEdQsGLOEBAXuFv085End7H2T7SGkaEfTO1+QEARPw@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/2fd0442020d5b23609873f999b7d374875875689.camel%40cybertec.at>
Precedence: bulk

On Mon, 2026-04-13 at 18:25 +0530, Raj wrote:
> When customer says they are facing slowness, what all wee need to check i=
n
> postgres db with 3 node patroni set up (sync between 1 and 2) - async wit=
h 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 couple of=
 hrs of issue window.
>=20
> Should we start with pgstatstatements and logs or how is it. Help.me high=
t level what all I need to check

You have to figure out *what exactly* is slow.  The customer has to tell yo=
u which
statements are slow. The parameter "log_min_duratoin_statement" might help.

Then you have to tune those statements.

Yours,
Laurenz Albe