| From: | Raj <rajeshkumar(dot)dba09(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Slowness |
| Date: | 2026-04-13 16:35:53 |
| Message-ID: | CAJk5AtZ_7nKTLpVvduJCeVD=qMD=A9nVia=UmCWGo6JkbRMoRQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(dot)albe(at)cybertec(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-04-13 17:11:06 | Re: Slowness |
| Previous Message | AJ Weber | 2026-04-13 13:09:05 | sslmode - detecting local docker |