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 1tICmC-00Csy8-57 for pgsql-hackers@arkaria.postgresql.org; Mon, 02 Dec 2024 20:12:12 +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 1tICm9-0030UE-M4 for pgsql-hackers@arkaria.postgresql.org; Mon, 02 Dec 2024 20:12:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tICm9-0030U5-5m for pgsql-hackers@lists.postgresql.org; Mon, 02 Dec 2024 20:12:10 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tICm7-000hx8-D5 for pgsql-hackers@postgresql.org; Mon, 02 Dec 2024 20:12:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1733170326; bh=EcjEuaFkCCNXrMNCKnHf17a9G4CiPiKrVVLQsulNMsg=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=yvjdkOF/IrZnPjY9uZia4rn7uBEahjRKphvw/lzLZyBZs8t/uZR6OYGA06gNB6X2W qeZYB3c6byiC1lPRG4wyRc4DpXhgKCQdm+3m8avn75saenWNG/GBMGfv2R9GZcabbP ZxIXaJ93hetA5B0iQKyTAt8Upih9k2ZL2LoVvMoTjD6loTQ0re65WpHTGGODVQdVcc sjCmPH+URTG03c3bEJcH/9K1uEvADh6JPhSn2FDRxxoTfJPdVQ9xbE1jQBgRLiWSWM GKZMVd+51r15a10fRTwZT5B1XbeykNtXegDMakCHZXjLmDaFkQE0w5Iy5DHXykcQTO ugcwpcJKofGPQ== Received: from [172.20.10.4] (unknown [89.113.152.1]) (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 255AF60784; Mon, 2 Dec 2024 23:12:06 +0300 (MSK) Content-Type: multipart/alternative; boundary="------------Gcn1y04SICcD0p2ihyQCLWRP" Message-ID: <30d54302-9e9c-4e04-819e-a13b679cdcc8@postgrespro.ru> Date: Mon, 2 Dec 2024 23:12:05 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Vacuum statistics To: Alexander Korotkov Cc: Jim Nasby , Andrei Zubkov , Masahiko Sawada , Melanie Plageman , jian he , pgsql-hackers , a.lepikhov@postgrespro.ru References: <9b10c6d3-52c4-4eef-b67c-c33442667729@postgrespro.ru> <9485d892-fd04-4e3a-ac24-7dd767cb7333@postgrespro.ru> <0B6CBF4C-CC2A-4200-9126-CE3A390D938B@upgrade.com> <6732acf8ce0f31025b535ae1a64568750924a887.camel@moonset.ru> <5AA8FFD5-6DE2-4A31-8E00-AE98F738F5D1@upgrade.com> <85b963fe-5977-43aa-9241-75b862abcc69@postgrespro.ru> <9C7A167C-DCDE-4A17-9ABE-6276723FEC50@upgrade.com> <2d493cf9-9ba7-4cc1-a3f2-67afd7c163ee@postgrespro.ru> Content-Language: en-US From: Alena Rybakina In-Reply-To: X-KSMG-AntiPhishing: NotDetected, bases: 2024/12/02 14:09: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: 2024/12/02 15:48:00 #26928591 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. --------------Gcn1y04SICcD0p2ihyQCLWRP Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 02.12.2024 11:27, Alexander Korotkov wrote: > Hi, Alena! > > On Wed, Nov 13, 2024 at 6:21 PM Alena Rybakina > wrote: >> Updated 0001-v13 attached, as well as the diff between v12 and v13. >> >> Thank you) >> >> And I agree with your changes. And included them in patches. > Thank you for the updated patchset. Some points from me. > > * I've read the previous discussion on how important to keep all these > fields regarding vacuum statistics including points by Andrei and Jim. > It still worrying me that statistics volume is going to burst in about > 3 times, but I don't have a particular proposal on how to make more > granular approach. I wonder if you could propose something. > * Previously PGSTAT_FILE_FORMAT_ID got increased by 1. Your 0001 patch > increases it by 2. It's minor note, but I'd like to keep the > tradition. > * Commit message for 0001 looks nice, but commit messages of 0002, > 0003, and 0004 look messy. Could you please, rearrange them. > * The distinction between 0001 and 0002 is not clear. The first line > of 0001 is "Machinery for grabbing an extended vacuum statistics on > heap relations", the first line of 0002 is "Machinery for grabbing an > extended vacuum statistics on heap and index relations." I guess 0001 > should be about heap relations while 0002 should be about just index > relations. Is this correct? > * I guess this statistics should work for any table AM, based on what > has been done in relation_vacuum() interface method. If that's > correct, we need to get rid of "heap" terminology and use "table" > instead. > * 0004 should be pure documentation patch, but it seems containing > changes to isolation tests. Please, move them into a more appropriate > place. > Thank you for your valuable feedback, I am already carefully processing your comments and will update the patches soon. I will think about what can be done to address the problem of increasing the volume of statistics; perhaps it will be possible to implement a guc that, when enabled, will accumulate additional information on vacuum statistics. For example, this way you can group statistics by buffers and vacuum statistics. -- Regards, Alena Rybakina Postgres Professional --------------Gcn1y04SICcD0p2ihyQCLWRP Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 02.12.2024 11:27, Alexander Korotkov wrote:
Hi, Alena!

On Wed, Nov 13, 2024 at 6:21 PM Alena Rybakina
<a.rybakina@postgrespro.ru> wrote:
Updated 0001-v13 attached, as well as the diff between v12 and v13.

Thank you)

And I agree with your changes. And included them in patches.
Thank you for the updated patchset.  Some points from me.

* I've read the previous discussion on how important to keep all these
fields regarding vacuum statistics including points by Andrei and Jim.
It still worrying me that statistics volume is going to burst in about
3 times, but I don't have a particular proposal on how to make more
granular approach.  I wonder if you could propose something.
* Previously PGSTAT_FILE_FORMAT_ID got increased by 1. Your 0001 patch
increases it by 2.  It's minor note, but I'd like to keep the
tradition.
* Commit message for 0001 looks nice, but commit messages of 0002,
0003, and 0004 look messy.  Could you please, rearrange them.
* The distinction between 0001 and 0002 is not clear. The first line
of 0001 is "Machinery for grabbing an extended vacuum statistics on
heap relations", the first line of 0002 is "Machinery for grabbing an
extended vacuum statistics on heap and index relations."  I guess 0001
should be about heap relations while 0002 should be about just index
relations.  Is this correct?
* I guess this statistics should work for any table AM, based on what
has been done in relation_vacuum() interface method.  If that's
correct, we need to get rid of "heap" terminology and use "table"
instead.
* 0004 should be pure documentation patch, but it seems containing
changes to isolation tests.  Please, move them into a more appropriate
place.


Thank you for your valuable feedback, I am already carefully processing your comments and will update the patches soon.

I will think about what can be done to address the problem of increasing the volume of statistics; perhaps it will be possible to implement a guc that, when enabled, will accumulate additional information on vacuum statistics. For example, this way you can group statistics by buffers and vacuum statistics.
-- 
Regards,
Alena Rybakina
Postgres Professional
--------------Gcn1y04SICcD0p2ihyQCLWRP--