Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lCFtx-0006Cb-Fs for pgsql-docs@arkaria.postgresql.org; Wed, 17 Feb 2021 06:01:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lCFtw-0007Al-Ct for pgsql-docs@arkaria.postgresql.org; Wed, 17 Feb 2021 06:01:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lCFtw-0007Ae-4b for pgsql-docs@lists.postgresql.org; Wed, 17 Feb 2021 06:01:28 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lCFtt-0000TG-Oo for pgsql-docs@lists.postgresql.org; Wed, 17 Feb 2021 06:01:27 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 620FF3A9; Wed, 17 Feb 2021 01:01:23 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 17 Feb 2021 01:01:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=QmoCvDLRY4xLyp8ZPYUwUbKuthr xdCPVW4mrdsJTNgc=; b=cDB/iJdVCoW41nLva1KC4E/qP/8dagnoZzdGJ6GriDA lH9RkWQ66WIRdSzn+deUbpI8GwCQpSPSqmnUYOT/05hy4cbV6S4gevo02/jAJhuM Vh7qHmNTA66UR5rRRckwNYl6HX4mzHAg+WVhfjLWWb0USUJyc6+3+SaaHQ0C6UyB gNu+uqsKuvg8Ung75gFeKJX3FBH4TsVEQlH5G5/GubehJgCEIRK4eYum9zfzmS/W MyTOJ31JBVTcRzFtiTFvrcQHdax7LsFJGUifwHnAL4ZxF/+na64T0xIQP/ibMBlo aOAzRk9OwtcEr4NtHB41CTwF2oq4/0vNqqOiCf7ZCUQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=QmoCvD LRY4xLyp8ZPYUwUbKuthrxdCPVW4mrdsJTNgc=; b=h1ICuTfydDUFQH0KM0evlr V/M+0TyzoPx6lyvy+xIM9UdlFpIoOTdXuPz4itbDOs5tMLzWUDYFWf2n+tDEa7TG bbOvnwABZlPtZQA9MrY3pEO8UGUXeAoMZ91vz3mXgF4NJq+wcy65R22YBfz23gcj uKSNYQyHBMIvu8g/O7HILGpQFRc/VaumDVrgELqWtfGKXoD0bmCS+Va3lvmXkmCw wR+NX3DYz3luFgf35GUz6sD/qDjpovUm1zqUbC/bEvQ4fSjsumTdwmdoir4w/Gyj 6Gyv/BawgzwhsSxK8D4BJoeyrxScVM3I+RIij6CwCH/gF1mGPmHX7w23RNn1d65A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjedugdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdefhedmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnh eptedugfetueeltefhtdefiefhgfdtteffkeeileeiieejjeettefhjedtteeffeeknecu ffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphepudduuddruddtvddrudektddrud ekheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm ihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id C4C971080063; Wed, 17 Feb 2021 01:01:21 -0500 (EST) Date: Wed, 17 Feb 2021 15:01:18 +0900 From: Michael Paquier To: kuzmin.db4@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Inaccuracy in wal_receiver_status_interval parameter description Message-ID: References: <161346024420.3455.1345266601055047937@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cd/K8HIeKVFVed0n" Content-Disposition: inline In-Reply-To: <161346024420.3455.1345266601055047937@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --cd/K8HIeKVFVed0n Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 16, 2021 at 07:24:04AM +0000, PG Doc comments form wrote: > The documentation says that setting wal_receiver_status_interval to 0 > disable updates of replication status completely. However walreceiver keep > sending status in some cases. For example, when startup has finished > processing WALs and start waiting for more: > https://github.com/postgres/postgres/blob/master/src/backend/access/transam/xlog.c#L12598-L12609 > It would be helpful to document in what cases status updates are still being > sent. The docs say only that: "Updates are sent each time the write or flush positions change, or at least as often as specified by this parameter." So it could make sense to complete a bit this paragraph with some words about the places where WalRcvForceReply() or similar logic is used. The case of the end of the WAL stream ending would be an extra one. How would you formulate that and what are the cases you think would be worth mentioning? -- Michael --cd/K8HIeKVFVed0n Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmAssS4ACgkQnvQgOdby QH16lQ/8DfWefNdqvs+mipB8gtPt2B2vyR8uFh2efaAqsiwPccEafERAk7BfdD+L xGBe4JlXhwFxdeY+bpg8NfxwOkW9gskpTPX/ocshvs4MKbQGszfULvZpf+w1ynSG /SX2y6Ryojtb8iMsWJhMjpWqziCO6RqQWuVFK6/uhVA53T03hDSoRA73928qH5DJ FohB+CxpZRIZAn9PCFLCLol14PqZhFt5T3oG0NpnV896RVEZTwd2ABHIunlWAlkh sLjJcm/5sbKxXevcPryWEmdY6MO8D1bVNn5WJVbpM4sahKB4bs5OngY0JRlDYonU inNCYGVlQ2xvdikRGzYHKGc7RSADNhhQw4Dc7F0HbfT8ZUXC7kWUFagOQWQM9M5s nGVubfTTS1HpJPLNUkspjpjoXxpcqtiv0zf6SRdLQfBFesBIoGmvfzZXMh0of2KX oyy++Rchb+nU68+frWigyFpgbz9SFX7YV5fbHsoQ5bTzLX1NBknznMQk4KqynhJr dN1KWMoxrPCGgQLF/aN/3j6j1gWAYDy1YLhVGk05ezGPjHwQ6uMFDZi9GWQJyN5d E3i7FRhs4UC1ueFcR/mnm1I1iZAQOFiR9PY0ZuIlL5wDLpz2XT571TjS/+RAUFKk DlE5UIlNRROQp8T//IOFiLeRqUydoErhaB5vmo9X+5XNEZO+joQ= =X/DP -----END PGP SIGNATURE----- --cd/K8HIeKVFVed0n--