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 1sRn0i-0016tq-Mi for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jul 2024 06:10:32 +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 1sRn0h-00BRdY-75 for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jul 2024 06:10:31 +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 1sRn0g-00BRdQ-TY for pgsql-hackers@lists.postgresql.org; Thu, 11 Jul 2024 06:10:30 +0000 Received: from mail-wr1-x432.google.com ([2a00:1450:4864:20::432]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sRn0d-001UO0-LJ for pgsql-hackers@lists.postgresql.org; Thu, 11 Jul 2024 06:10:29 +0000 Received: by mail-wr1-x432.google.com with SMTP id ffacd0b85a97d-367a464e200so205417f8f.2 for ; Wed, 10 Jul 2024 23:10:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720678225; x=1721283025; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=TMmC4pqM74sbpcTyCw70IzgSm8ecL3LH54KtXQpz27w=; b=Gk/HhKSfofLkbGPQoTH+nZXOYms/CS8B8aq/Bla73U45oROqz2FGTaaoxZoO3b4HKo DMK0sGMBGGlvOgSyC/BCJDJQYE3jlrw3iemqJFWgRWq0gb+BDO4GE0+9xnEVBoAcG0rl eHdUSnJlrsYXf0veL08grW8op9cNY9VUATKpaTSm+nB7xwuNrAa+EcZWMcrRIrrzjU8B grY964ZZ6D2CLZkqIn/0PUJCC3CT6/Dl0Li8NEJ9SpOKqXl1egeeUTAI7bGrTqgdiSkb +tDsUv/Kq35SD17yxJegy+PqCzQjIYFZxLEqE4c/VDbXQ7+eRDNVEY6Qdbid4rd662qJ Dnnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720678225; x=1721283025; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=TMmC4pqM74sbpcTyCw70IzgSm8ecL3LH54KtXQpz27w=; b=DysmHkNvCG5SQMrvqP3eLPIT/iHr+geKUcyazYMRWpXHCpSNzN+Gb9/OEhg3U2BTxd SXMytVZTrdv/HdpZ/bnOdrX1M105e2QN783e3t7P7Ju37a80S5YMcaMJAhwaMPmixJ3O XaN8Z7FAsItvydVMPPYbroj26gLVumKXHnQpjlHObA1emxqbFsgeIseXDXggES9HQGCW Cm85ptmjgOSpX9ncWMJGHGoygn89JdpC517ySE/d+sf2dfapRyey3i4dMdbz63ceEY3w 4PoFTiKQFD3u+mdzJsSVDkGiqKR7z8SreornOS90OrNuowNbgLhE7QOAB8FrcyRjcBpp NAAw== X-Gm-Message-State: AOJu0YzoFvqiW+Px1HiE0WZF4U+bpAxlxxMOdZ2n32zjTvveCNtJ+5qs +lVtoaqsTzthPHNgLD3LxxfDykPSYBxZPj22ZWw6+ixWeepvAQqk8lK4jg== X-Google-Smtp-Source: AGHT+IH7T+ZT9xIKLFesrHVx1XH4MDJra4tR+chqG26CzDNiSToTBYEA8wjqRewnesZCe3Cbf0sglQ== X-Received: by 2002:a5d:4525:0:b0:367:4dce:1ff5 with SMTP id ffacd0b85a97d-367cea91fbfmr4748121f8f.32.1720678224878; Wed, 10 Jul 2024 23:10:24 -0700 (PDT) Received: from ip-10-97-1-34.eu-west-3.compute.internal (ec2-15-236-134-5.eu-west-3.compute.amazonaws.com. [15.236.134.5]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-367cde89198sm6804221f8f.60.2024.07.10.23.10.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Jul 2024 23:10:24 -0700 (PDT) Date: Thu, 11 Jul 2024 06:10:23 +0000 From: Bertrand Drouvot To: Michael Paquier Cc: pgsql-hackers@lists.postgresql.org Subject: Re: relfilenode statistics Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Thu, Jul 11, 2024 at 01:58:19PM +0900, Michael Paquier wrote: > On Wed, Jul 10, 2024 at 01:38:06PM +0000, Bertrand Drouvot wrote: > > So, I think it makes sense to link the hashkey to all the RelFileLocator > > fields, means: > > > > dboid (linked to RelFileLocator's dbOid) > > objoid (linked to RelFileLocator's spcOid) > > relfile (linked to RelFileLocator's relNumber) > > Hmm. How about using the table OID as objoid, The issue is that we don't have the relation OID when writing buffers out (that's one of the reason explained in [1]). [1]: https://www.postgresql.org/message-id/Zl2k8u4HDTUW6QlC%40ip-10-97-1-34.eu-west-3.compute.internal Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com