Re: Slowness

"All the stakeholders" decide the threshold. For example, if *they*
complain about queries taking more than 2 seconds, you obviously shouldn't
set log_min_duratoin_statement to 5 seconds.

If they don't know, are too clueless to know, or it's a mixed OLTP &
reporting database, pick a reasonable value and go from there.

You can always change it later...

On Mon, Apr 13, 2026 at 12:36 PM Raj <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:

> 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
>>
>

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!