public inbox for pgsql-admin@postgresql.org  
help / color / mirror / Atom feed
From: Ron Johnson <ronljohnsonjr@gmail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Slowness
Date: Mon, 13 Apr 2026 13:11:06 -0400
Message-ID: <CANzqJaC=321==QbieX7soJzqycpFXWyFURkquWdk0+MUvSe=Lw@mail.gmail.com> (raw)
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>

"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.dba09@gmail.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.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
>>
>

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


reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Slowness
  In-Reply-To: <CANzqJaC=321==QbieX7soJzqycpFXWyFURkquWdk0+MUvSe=Lw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox