Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfIdF-001CmO-7w for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Feb 2025 13:06:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tfIdE-003M3a-Bc for pgsql-hackers@arkaria.postgresql.org; Tue, 04 Feb 2025 13:06:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tfIdD-003M3Q-T6 for pgsql-hackers@lists.postgresql.org; Tue, 04 Feb 2025 13:06:24 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tfIdA-0037lW-2j for pgsql-hackers@postgresql.org; Tue, 04 Feb 2025 13:06:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1738674377; bh=AsM27EYk5G+ynrs2pHzlD+XHN8A8Vbtxr8gqr8aIOLw=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=uSAWexXUzSXK9zqU5H0nOTS9o4CJgdWh2V0oTxeMhbFakt7hCaC1qBcVTgP8x/0oW /9PWofgNVSKqdF9sLukbw0Lb4cPpWo/WO6zEA6JwpmimkLVWH3HB9GPMevtZR7OKKl n0tDiwZpvKSNlZs5nYdpeKSzAbXbgDAeFErT3dpf9emOt3Fdl4ppsssLjdcC0XIgt2 OxHjdQTcz3lY9HNd84Cl4AZvF1QrtWGg62OihmkqQziXA4MesIv2p5LE075fgnLzsV AcWmVTPiPrBbOeb2eLRd1fjjMuLRA5b5HYfH10IkSVYp5i4tQE8e7pQL9s9qIL1Za9 jT7VWmCVPW7aw== Received: from [172.20.10.4] (unknown [89.113.145.182]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: a.rybakina@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 34A7A60857; Tue, 4 Feb 2025 16:06:17 +0300 (MSK) Content-Type: multipart/alternative; boundary="------------QyyztsSU405FBr4dEBzvJel6" Message-ID: Date: Tue, 4 Feb 2025 16:06:15 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: POC: track vacuum/analyze cumulative time per relation To: Michael Paquier Cc: Bertrand Drouvot , pgsql-hackers , Sami Imseih References: Content-Language: en-US From: Alena Rybakina In-Reply-To: X-KSMG-AntiPhishing: NotDetected, bases: 2025/02/04 09:43:00 X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.1.0.7854, bases: 2025/02/04 11:12:00 #27207681 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------QyyztsSU405FBr4dEBzvJel6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi! On 28.01.2025 03:59, Michael Paquier wrote: > On Mon, Jan 27, 2025 at 11:22:16AM -0600, Sami Imseih wrote: >>> I have put my hands on this patch, and at the end I think that we >>> should just do the attached, which is simpler and addresses your >>> use-case. Note also that the end time is acquired while the entries >>> are not locked in the report routines, and some tweaks in the docs and >>> comments. >> Thanks for the update. This LGTM. > Okidoki. Done, then, with bumps for the catalog version and the stats > file version. You might be interested in looking at my patch for collecting vacuum statistics? Same issue, but it collects more information about the vacuum procedure for relations and databases. I mentioned it here [0] in the current thread. [0] https://www.postgresql.org/message-id/Z4U3hkWuEgByhGgJ%40ip-10-97-1-34.eu-west-3.compute.internal -- Regards, Alena Rybakina Postgres Professional --------------QyyztsSU405FBr4dEBzvJel6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Hi!

On 28.01.2025 03:59, Michael Paquier wrote:
On Mon, Jan 27, 2025 at 11:22:16AM -0600, Sami Imseih wrote:
I have put my hands on this patch, and at the end I think that we
should just do the attached, which is simpler and addresses your
use-case.  Note also that the end time is acquired while the entries
are not locked in the report routines, and some tweaks in the docs and
comments.
Thanks for the update. This LGTM.
Okidoki.  Done, then, with bumps for the catalog version and the stats
file version.

You might be interested in looking at my patch for collecting vacuum statistics? Same issue, but it collects more information about the vacuum procedure for relations and databases.

I mentioned it here [0] in the current thread.

[0] https://www.postgresql.org/message-id/Z4U3hkWuEgByhGgJ%40ip-10-97-1-34.eu-west-3.compute.internal

-- 
Regards,
Alena Rybakina
Postgres Professional
--------------QyyztsSU405FBr4dEBzvJel6--