public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Shenavai, Manuel <[email protected]>
To: Achilleas Mantzios <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Autovacuum, dead tuples and bloat
Date: Wed, 26 Jun 2024 08:05:26 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <AM9PR02MB7410F28F66A98C62CBAF3020E8D62@AM9PR02MB7410.eurprd02.prod.outlook.com>
References: <AM9PR02MB7410603C5F467DED657D5330E8C82@AM9PR02MB7410.eurprd02.prod.outlook.com>
	<[email protected]>
	<AM9PR02MB7410AA1DEA442AED52FBB5E9E8C92@AM9PR02MB7410.eurprd02.prod.outlook.com>
	<[email protected]>
	<AM9PR02MB7410F50DD4C2AFBD1E6C9032E8CA2@AM9PR02MB7410.eurprd02.prod.outlook.com>
	<[email protected]>
	<AM9PR02MB7410F28F66A98C62CBAF3020E8D62@AM9PR02MB7410.eurprd02.prod.outlook.com>

On 6/26/24 00:03, Shenavai, Manuel wrote:
> Thanks for the suggestions.
> I checked pg_locks  shows and pg_stat_activity but I could not find a LOCK or an transaction on this (at this point in time).
> 
> I assume that this problem may relate to long running transactions which write a lot of data. Is there already something in place that would help me to:
> 1) identify long running transactions
> 2) get an idea of the data-volume a single transaction writes?
> 
> I tested the log_statement='mod' but this writes too much data (including all payloads). I rather would like to get a summary entry of each transaction like:
> "Tx 4752 run for 1hour and 1GB data was written."

https://www.postgresql.org/docs/current/runtime-config-logging.html

log_min_duration_statement

Read the Note below the entry.

This will log long running queries, though it will not show th amount of 
data written.

If you want to go more in depth there is:

https://www.postgresql.org/docs/current/pgstatstatements.html

It is an extension that you will need to install per instructions at the 
link.

> 
> Is there something like this already available in postgres?
> 
> Best regards,
> Manuel

-- 
Adrian Klaver
[email protected]

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Autovacuum, dead tuples and bloat
  In-Reply-To: <[email protected]>

* 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