Date: Wed, 25 Jan 2023 19:13:49 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: Clive Swan <cliveswan@gmail.com>,
	"pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: Long running queries
Message-ID: <Y9HFvR145+1+MeOm@momjian.us>
References: 
 <CWXP123MB395950C601C6F6D02AFA913EA0CE9@CWXP123MB3959.GBRP123.PROD.OUTLOOK.COM>
 <8299AF9E-0269-4F02-BC0D-D86D0D817D86@elevated-dev.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8299AF9E-0269-4F02-BC0D-D86D0D817D86@elevated-dev.com>
Archived-At: 
 <https://www.postgresql.org/message-id/Y9HFvR145%2B1%2BMeOm%40momjian.us>
Precedence: bulk

On Wed, Jan 25, 2023 at 10:57:58AM -0700, Scott Ribe wrote:
> > On Jan 25, 2023, at 10:55 AM, Clive Swan <cliveswan@gmail.com> wrote:
> > 
> > SQL Server has a handy SQL "tool" to spot expensive and/or long running queries.
> > 
> > Is there a similar query/tool for Postgresql??
> 
> - pg_stat_statements extension
> - log_min_duration config parameter

FYI, log_min_duration_statement will not print the duration until the
query completes, so it is good for analysis later.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

Embrace your flaws.  They make you human, rather than perfect,
which you will never be.