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 1kfMMo-0006RH-Kj for pgsql-performance@arkaria.postgresql.org; Wed, 18 Nov 2020 12:15:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kfMMn-0006jB-Gb for pgsql-performance@arkaria.postgresql.org; Wed, 18 Nov 2020 12:15:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kfMMn-0006j4-9A for pgsql-performance@lists.postgresql.org; Wed, 18 Nov 2020 12:15:17 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kfMMk-0000Ci-IL for pgsql-performance@postgresql.org; Wed, 18 Nov 2020 12:15:16 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 587BA5C01A5; Wed, 18 Nov 2020 07:15:13 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 18 Nov 2020 07:15:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imap.cc; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=z n1WubQq139ppAXjyPHtPXCm46dQ5F2cULD9N9IJtPA=; b=YpNqa7/ByaKVPgbhA r2vzNvIGzAJ8zWSaVjdXA5VSrKx81fMVYuNETUBprfPOTJ7mW2wy6eCsDy9a+NbU eDuPOYPfaB+hkJ9jBh7brxwldP/lI49J1Kt6lorNS4IBHTQZbMbt4XHlne5eXl33 C4KKT2QCPkbmrFF5nZ21szTj9ONgKCDx2CwEuiAGZcNyWfs/SYhUxhkCk8Xwohq2 ptqF0cwhAw53RbdbWYyyzSIBUoQBk8XZt0lW7lntxO3QkFz+gStEMY3QmK4y9jiN UKC3jgPqqi9yi6CH/fvwYlykCrCdn+BYw7f9Tn8NS7xLAiQkF2HEoRniYxy8a7xL EYluw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm1; bh=zn1WubQq139ppAXjyPHtPXCm46dQ5F2cULD9N9IJt PA=; b=cHUBeOmc45VqwAVVnYKEpgt1KtlZIVqtpo9W+EqT+gapZLMtCxkfX0owL 7oxPp0t447C2yp0WFhJVYiDd/zWw0JIodmX6N/FTrDhfb9+BD88gL9BTpv2Cxop6 BzGyGQghvO9J+u5tVoFz9Xz7pWKhtmMZCe1ntUiOIr4Ijpn8s1ab5lHwQHjWnNXh 6vnP0EzTowaoNIPY/utjMWeXFbarLzp7o0ORzB4yLCeAz86gQ1fv32meaHTXGPd1 eHbBYB0VaQoUPptC2FJ1SuLuf9kj0zbOcpqy5C4xB2kYYp08yb64wUGSejoK030W HnKEoAxVufOKF4sN7QUshybYaERzw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudefhedgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdludehmdenucfjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddt feejnecuhfhrohhmpeetlhgvgigvhicuuegrshhhthgrnhhovhcuoegsrghshhhtrghnoh hvsehimhgrphdrtggtqeenucggtffrrghtthgvrhhnpeegffekveejveeuveeffefhgeei udduvdelkeelvdegiefhkeeugeffleffjeegheenucffohhmrghinhepphhoshhtghhrvg hsqhhlrdhorhhgnecukfhppeelvddruddvrddvrddvkeenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsrghshhhtrghnohhvsehimhgrphdrtg gt X-ME-Proxy: Received: from ev9d9.btn1.brandwatch.net (host-92-12-2-28.as43234.net [92.12.2.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 5D0473064AAA; Wed, 18 Nov 2020 07:15:12 -0500 (EST) Subject: Re: How to prioritise walsender reading from pg_wal over WAL writes? To: Laurenz Albe Cc: pgsql-performance@postgresql.org References: <774ec1b8-c7c6-cfa2-098d-5c6a32dcfc1a@imap.cc> From: Alexey Bashtanov Message-ID: Date: Wed, 18 Nov 2020 12:15:11 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Sorry Laurenz, My reply did not get threaded appropriately. My original question was here: https://www.postgresql.org/message-id/a74d5732-60fd-d18b-05fd-7b2b97099f19%40imap.cc I'd like to prioritize walsender for replication not to lag too much. Otherwise, when I have load spikes on master, standby lags, sometimes by hundreds of gigabytes. Best, Alex