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 1tH3IJ-002rGK-1l for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Nov 2024 15:52:35 +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 1tH3IF-008jop-RU for pgsql-hackers@arkaria.postgresql.org; Fri, 29 Nov 2024 15:52:33 +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 1tH3IF-008jog-Hc for pgsql-hackers@lists.postgresql.org; Fri, 29 Nov 2024 15:52:32 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tH3IA-000AiA-8L for pgsql-hackers@lists.postgresql.org; Fri, 29 Nov 2024 15:52:32 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-2ffc1f72a5bso20623851fa.1 for ; Fri, 29 Nov 2024 07:52:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732895545; x=1733500345; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Dub/CLmGr9qUs5zIzzHrZZu8f8bLx3piAjJ9sGJGD7Y=; b=ZIllAg15u1lZ2SWiJNzO632gKzsc3m/daJM1scXfs6+6EAVx13gk0yYXwEa0s7q9le W1Q2pFWUbDGhLYbJyiJ+OXz0HH+zY6KnrKmO5P4ijNgdYcxkIGKLSJiH3zziTcuHceok VQr0Zs0ZwEHFmttr/kZHV9OMXcy1bZxiHWHM0faNxoQsYtbQBlzi36SwMjCXHqSDe7Ge XpkegPE9p4z5CeJTrH0k4KrGKf5SRIESV6eQXDBTJLrxcr/Td5FsZ/HKfjHX8d37fKLq d609wbaiPA+98CIuwM2QlFs16kBpNV7mM9p+Rz5rS3tes1HeOSanGGyC4oXu6i6g9pVz PLrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732895545; x=1733500345; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Dub/CLmGr9qUs5zIzzHrZZu8f8bLx3piAjJ9sGJGD7Y=; b=lcAb1Z+unTkdvK6pwIEDpV/9JI+K46Wm5v0nDk31G002JUorkBKn7jQguviI991FbD EY872rKeydc7fUP9SOu4gDSWRRBTRB+94A2V6RcnsE6Xf+1kUhxZvkj/+a0LUmeATGmW +/yLztFXOXly38aexPe30xRvtP0U/m0VUfUQuiZ3wNUnw52A6OpsHXSo+uu4U5wwebX6 44bsaG+oxFJI3h81BXsbldCCR0vD8fKqsCRliseg0bKsBLgLIE9nY3ITbo45ZYg9aMhQ xnYpOPRM3/VKPAI8VkkCgLxbcyX9bBTEMwfpJuy9HFA5fvb6ljEIEOUkOz6+eMntlc4e gQ7w== X-Forwarded-Encrypted: i=1; AJvYcCVOvnWdeSiivZwbnO4S11YRtUd8MAiB/ACsZVk7EN17T2LtzJcAadY7wJWH72Dljk/3YRxkdHR1QYS5p1gt@lists.postgresql.org X-Gm-Message-State: AOJu0Yz97M8bhYCjmVFIA+NDLanmHRjIb3yqHIDc1UACpZ8u297R6LG5 7CzGUekKjaH1N9G557MGAWZrqXdintTrGDn8YbS85MqB0lcei1Z8WRGrWh26ewh8z2wGUh9IqeM 5esRNSCoys+sooFn6GuSIi5RwJVj1M2QuLy0= X-Gm-Gg: ASbGncuLuma8f9pI9E0Zkio0io9ckakOvQ6VekW8i8dLclwCf8RyT8Wdujp27B8+zFn MwToNKYZ+TMsjum1uzpUz2doAo4/c X-Google-Smtp-Source: AGHT+IEfP2vbaC1IrzI7rzQq1okwI4gxjiI2iOmRAUp/9MYw7/I/DNSJj2IVXiqgbwqSe4lPhqxBX2bO6Fe3rk7Czow= X-Received: by 2002:a05:651c:542:b0:2ff:d2d7:ef91 with SMTP id 38308e7fff4ca-2ffde213f74mr26429731fa.11.1732895545085; Fri, 29 Nov 2024 07:52:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kirill Reshke Date: Fri, 29 Nov 2024 20:52:13 +0500 Message-ID: Subject: Re: relfilenode statistics To: Bertrand Drouvot Cc: Robert Haas , Michael Paquier , pgsql-hackers@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 29 Nov 2024 at 20:20, Bertrand Drouvot wrote: > On Fri, Nov 29, 2024 at 11:23:12AM +0500, Kirill Reshke wrote: > > If we don=E2=80=99t have the relation OID when writing buffers out, can= we > > just store oid to buffertag mapping somewhere and use it? > > Do you mean add the relation OID into the BufferTag? While that could pro= bably > be done from a technical point of view (with probably non negligible amou= nt > of refactoring), I can see those cons: Not exactly, what i had in mind was a separate hashmap into shared memory, mapping buffertag<>oid. > 2. Probably lot of refactoring > 3. This new member would be there "only" for stats and reporting purpose = as > it is not needed at all for buffer related operations To this design, your points 2&3 apply. --=20 Best regards, Kirill Reshke