Re: POC: track vacuum/analyze cumulative time per relation

From: Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sami Imseih <samimseih(at)gmail(dot)com>
Subject: Re: POC: track vacuum/analyze cumulative time per relation
Date: 2025-02-04 13:06:15
Message-ID: b2be6254-c977-4329-b62f-c35ba8772641@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2025-02-04 13:24:03 Re: Avoid orphaned objects dependencies, take 3
Previous Message vignesh C 2025-02-04 13:01:19 Re: Restrict publishing of partitioned table with a foreign table as partition