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 1tpnra-00CNLN-I9 for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Mar 2025 12:28:38 +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 1tpnrY-009mf5-S1 for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Mar 2025 12:28:36 +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 1tpnrY-009mci-Hm for pgsql-hackers@lists.postgresql.org; Wed, 05 Mar 2025 12:28:36 +0000 Received: from fhigh-b4-smtp.messagingengine.com ([202.12.124.155]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tpnrW-0016Pb-1T for pgsql-hackers@lists.postgresql.org; Wed, 05 Mar 2025 12:28:35 +0000 Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfhigh.stl.internal (Postfix) with ESMTP id 13A1425401BD; Wed, 5 Mar 2025 07:28:34 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Wed, 05 Mar 2025 07:28:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1741177713; x=1741264113; bh=Kt2mF1NnHI 3NhDnBJvlApU8Z2Cx8FXSXrl6e8UfxPaM=; b=oMg/QbhlgMJhDXJrJpG5TXJQQ4 vzpjzY0qVH2S6okOfjS3NtJDxWDIgFd0B2sWV1HxMsmbTTrRW0nGOwqVKp1KHoeB hTKXPhZ96sj3qTUp387BlMsPNE+tyFTJlmUCUPjdAJAjDMHXVFBPg4BPJV4ztyAf 6htDlMKjp37kM4BLcMtce30JsWsjmC04ItsnKafHJGadP9+e4aaYywm1/bPz0vv8 LMabZ/sYQBQxmwXw//qPg4YHLk597KN86HkHI/xLElpjQ+1PmeFsWmcTZsHGffwL Xf0LV4/qaTfbYz8yCMRacRPUkMNbsowX3kfPujmktzSeCnMmOr3q4yqMsqww== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1741177713; x=1741264113; bh=Kt2mF1NnHI3NhDnBJvlApU8Z2Cx8FXSXrl6 e8UfxPaM=; b=WRiN85WDkude2GMQ3yYI4YXQUT/DwNaDLQuKxeJ8AiCy5HVgj41 24JHYqrvsDpmhtEI9/tG0bsrDUidowgR0V7A9puvbazhN/DOMiji9WoBT/ennY/C H/VO9nVCVJb8hDIaTtZZFiHuKuMd+Lm8K0WjQc2QVcv8fv9jT6COTFnH550f4ehD 9kHP5jj/YqqsoQz/s9IcDbNwWNKQJRQs8picfzG8xL32KUg5N1lv3lcRSsclvBFv ZYVIodnNvLykIEVR3PcB6cq57VZeLUe7JCATcXoCpNI4UREBeB0QJ2tFbqJfk/4W X+WXsqpNyVNlopx7dGas6zkIg400C9MCULA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddutdegkeduucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpih gvnhhtshculddquddttddmnegfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefu kfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivg hruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhep teelieefudffhffhtdetleeggeegfffhkeeuveetiefgudduvedutefggeeivdejnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggv lhesphgrqhhuihgvrhdrgiihiidpnhgspghrtghpthhtohepvddpmhhouggvpehsmhhtph houhhtpdhrtghpthhtohepsggvrhhtrhgrnhguughrohhuvhhothdrphhgsehgmhgrihhl rdgtohhmpdhrtghpthhtohepphhgshhqlhdqhhgrtghkvghrsheslhhishhtshdrphhosh htghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Mar 2025 07:28:32 -0500 (EST) Date: Wed, 5 Mar 2025 21:28:23 +0900 From: Michael Paquier To: Bertrand Drouvot Cc: Postgres hackers Subject: Re: Monitoring gaps in XLogWalRcvWrite() for the WAL receiver Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2XO9DORml+ecJRoi" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --2XO9DORml+ecJRoi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 05, 2025 at 08:04:44AM +0000, Bertrand Drouvot wrote: > On Wed, Mar 05, 2025 at 12:35:26PM +0900, Michael Paquier wrote: > Also for sync? sync looks fine as issue_xlog_fsync() is being called in= =20 > XLogWalRcvFlush(), no? Yes, we're OK for the sync data aggregated in the WAL receiver on HEAD, as mentioned below, not in the back-branches. > We're not emitting some statistics, so I think that it's hard for users to > complain about something they don't/can't see. One would see idle data in pg_stat_wal on a standby, so the lack of data could be annoying, but I'm perhaps the only one who noticed that.. > Same logic as in XLogWrite() and I don't think there is a need for a=20 > dedicated wait event, so LGTM. Thanks. -- Michael --2XO9DORml+ecJRoi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmfIQ2cACgkQnvQgOdby QH02NA//Zf2M3DbCvwW3OP5W+5R27hYStyntkqGz0a2dXJfA9IycveHCEY4LazSN aAegGtrdDCdjjnmHtrYqx2DYbBwKb/vqVakti+82ucn9e+/xno0ILykltziOvYcX lwdwDH9gJmmLrnbLO0S0UgJrMZlZCdmR5UA04BKfH0etiVDAUOjbEje6NiRZX8We OFxesXx0IrF5naMZhKJtHDOP7UCldiKvqxnLadUXNNfKbA93ArIir24fYf8x0nUQ bmNfNtV/6XTL87XiW0ukMVZ4hOcDFiaaQ4qLs/EVff0XsJIvyJ7TIysS6ijFeNkY cSplnPoiPL1tV3r5SGHc1qdZNFVlN6UGJGw81zYid2C09marQnZV80fLOeBzwQk3 6ns+pU+MheI/SOojIr0s7ZWLaXaXUS2D//NmWlikEDmKM92wLVnH0rQD2W4aWLQo rEGMF1/lISBAKwfXT0JS7a0DBdM3lDDCS87or+/EEqxkPI3L+9jcDr8/+k2ZSFKk puyyLlkrJVWUvZVq5aKifBxr4IBbe7uk70gNKn8gZb95rIRrj6sF9DNGomGS5QpU hroPLUR8aB1dsOyFdv8Z5WFD6UH3vfXpTavqQg86/P0M0d0Rf8FivBOR6TrlEUly GQKFfGpZ5COKBvhtPABzqCQnbOTMBmFNId5OnLZCOvdn6orF2Qo= =3Cio -----END PGP SIGNATURE----- --2XO9DORml+ecJRoi--