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 1s4Yns-005CHH-Ul for pgsql-hackers@arkaria.postgresql.org; Wed, 08 May 2024 04:21:16 +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 1s4Ynp-006qIU-3b for pgsql-hackers@arkaria.postgresql.org; Wed, 08 May 2024 04:21:14 +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 1s4Yno-006qHK-NP for pgsql-hackers@lists.postgresql.org; Wed, 08 May 2024 04:21:13 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s4Ynm-0026YQ-4k for pgsql-hackers@postgresql.org; Wed, 08 May 2024 04:21:12 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a59cc765c29so693162766b.3 for ; Tue, 07 May 2024 21:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715142069; x=1715746869; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=S9F7OJkbepPC6QiUu0iXpfrraVZXGFjvq/c7ozI1RUQ=; b=ASCuJDoFaVpJjYwFW1tmAmjF/wCLKwo7g2+CBiUnyEdXSHGppOvsP557QqmsFWqxfn EhKpcBJTZZN1XFM1n+qPadQcMJdy4YmSF3ntEWqhVE6/ZD+xCJWtJpDaDoPiqJ4EK4Js QJYh2AV0JjFBY/2pkQcXVHKyM6wFs9DtyJFp18JoD2xt1oWXDU8r7d/YWwfWSu2Wgbas 1ucmFwkbXZrY9tl+ktl19R1FDqTuIXVDAfJuS7WLDUEH3cULbMZ9eitSxXB0tHqhDKhr 5uNQbVt8oN7risq+v/zweQzYCPMXoMmRiZnj1UfPFk+k+QywcqdUCKJtTdoI9AeHqU6j +o6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715142069; x=1715746869; h=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=S9F7OJkbepPC6QiUu0iXpfrraVZXGFjvq/c7ozI1RUQ=; b=LtM4w5dRNSxBV/QPizeTChYNeCpTIiKBJ6uKsrCcKQFHCaFvCJLSpCOp5l4JLxAxv1 dW6S+sTtpQ97cDTB0AifJ+b84ljv0AkN08v8WKOP9UMAUksEZrka+iLHqfb7sPDRzubR jx1REPlyUoA9cWAGwtPfqxFUH/Mv4yfEldVe3cqCF6e23JLFoKvqbwcMbq0VbF66FOWk U7NLoS5kW59RbfE/PqtW6n+HSKinLk1wSvPM7zJqdwU8UNvI3cO47xeH97ahDSuI68Iq fO6CZ76yy5YsNFqsFqrx2GWdk4DkxibLVwW892gTQ7vjxhqL2X/M6OnJMtAu9Qjq0b97 yWNg== X-Gm-Message-State: AOJu0YxNCSxRZiaBukOBhC2yN8lQ+M4COvreUyPUsTpIspR3N7KFRyab kLYqX67ysbMZbIn0zfic6ln+ekZx57an0g6K5bqp/cqgB7GMtAqbUbtn5/UwDNlHD/Fs4p30r/t owCoNiINRAJVMhTriP8A04eBhbwc= X-Google-Smtp-Source: AGHT+IERa9csnDh3JNP1xXWU8xAflUZZZl6pNEsMGZUBn4OULuyr5vmMFGvrPQiDDcuWBuGOysaXf/382Or+IKXPgqc= X-Received: by 2002:a50:9313:0:b0:572:a0f6:c8a7 with SMTP id 4fb4d7f45d1cf-5731daa0d2fmr751681a12.42.1715142068732; Tue, 07 May 2024 21:21:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jingtang Zhang Date: Wed, 8 May 2024 12:20:56 +0800 Message-ID: Subject: Re: Use WALReadFromBuffers in more places To: Bharath Rupireddy Cc: PostgreSQL-development Content-Type: multipart/alternative; boundary="000000000000bf0c4c0617e9a15b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bf0c4c0617e9a15b Content-Type: text/plain; charset="UTF-8" Hi, Bharath. I've been testing this. It's cool. Is there any way we could monitor the hit rate about directly reading from WAL buffers by exporting to some views? --- Regards, Jingtang --000000000000bf0c4c0617e9a15b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi, Bharath. I've been testing t= his. It's cool. Is there any way we could
monitor the hit rat= e about directly reading from WAL buffers by exporting
to some vi= ews?

---

Regards, Jingtan= g

--000000000000bf0c4c0617e9a15b--