Re: Slowness - Mailing list pgsql-admin

From Raj
Subject Re: Slowness
Date
Msg-id CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com
Whole thread
In response to Re: Slowness  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Slowness
Re: Slowness
List pgsql-admin
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

pgsql-admin by date:

Previous
From: AJ Weber
Date:
Subject: sslmode - detecting local docker
Next
From: Ron Johnson
Date:
Subject: Re: Slowness