From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Clive Swan <cliveswan@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Long running queries
Date: Wed, 25 Jan 2023 10:57:58 -0700
Message-ID: <8299AF9E-0269-4F02-BC0D-D86D0D817D86@elevated-dev.com> (raw)
In-Reply-To: <CWXP123MB395950C601C6F6D02AFA913EA0CE9@CWXP123MB3959.GBRP123.PROD.OUTLOOK.COM>
References: <CWXP123MB395950C601C6F6D02AFA913EA0CE9@CWXP123MB3959.GBRP123.PROD.OUTLOOK.COM>
> 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
- pg_stat_activity view
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: scott_ribe@elevated-dev.com, cliveswan@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Long running queries
In-Reply-To: <8299AF9E-0269-4F02-BC0D-D86D0D817D86@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox