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 1qLJFS-002o1h-5e for pgsql-bugs@arkaria.postgresql.org; Mon, 17 Jul 2023 08:06:26 +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 1qLJFQ-006dEa-4D for pgsql-bugs@arkaria.postgresql.org; Mon, 17 Jul 2023 08:06:24 +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 1qLJFP-006dER-SN for pgsql-bugs@lists.postgresql.org; Mon, 17 Jul 2023 08:06:23 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qLJFO-0011gQ-CZ for pgsql-bugs@lists.postgresql.org; Mon, 17 Jul 2023 08:06:23 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id E302C320085B; Mon, 17 Jul 2023 04:06:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 17 Jul 2023 04:06:20 -0400 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:sender :subject:subject:to:to; s=fm3; t=1689581179; x=1689667579; bh=0U 5ezB6Da01ogJaob7pE5UZqI8KSEMZl3UI1Q5TYR7M=; b=rwWdDXmyCy1sQlT9td kzKXfDsxm9S6hyrLmeM5oLI+uo1Ju0TKtBW5FmKix1udhywKLUocrpAGPVoRB8Kz Z14a268i33jMj2QkMhWQipsHs3DP7mvzFH/0ZvDYs1koZGaZk1sX/IF9YNOCWdUk oRmvNcs0U+sllzdtva9yOsV35K5hyNVJQQ9I1HRMqbhVkVV8zcAtfnWCqhYIo7GM jO68mHCsm6doT4onlD+fMMz5I620ujIFIfKwKbqOtIOK6NlojvHvB41yxDkWJFjH USGO3iQsJND9uARZT4UHKHAqmNWap5d5mYNO7mA8gNhVAuoyP7V5UCMOLVZ4v2ne xYbw== 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:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1689581179; x=1689667579; bh=0U5ezB6Da01og Jaob7pE5UZqI8KSEMZl3UI1Q5TYR7M=; b=nS6ce117zmaFRgh1DuZZW36kGvm1A 917agVWncucnWBOpPfZcOCmm+Fuplt7QyNFoFkW4bB6tWGXiy6HAdvy8BU4MhZ3+ XqDohtTJjnnt0/95WICbuztvoBmdQts7O+odueoobcHR0tCbUfga9cw6Wn7rllTE qc5iGWfM1aNAh+S7aF8efwsRjtKZYp6L6L9BJG790cBe8oC/S5E+i0UF8QUSpZU8 vZeP3pecnw0OuhwXUJSikjaJRH6Kv8aCVwN8to99fBa6SR6eIrtdzyXczI8pE4c1 djPeLA4aT1be9+0OHRBv6dTr/a4VVBtHQA/XdkdjcL1FcWbZyuwOuEekw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrgedugdduvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 17 Jul 2023 04:06:18 -0400 (EDT) Date: Mon, 17 Jul 2023 17:06:15 +0900 From: Michael Paquier To: Laurenz Albe Cc: hargudekishor@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18025: Probably we need to change behaviour of the checkpoint failures in PG Message-ID: References: <18025-85e7e63f3ff93d40@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="F6DilIiYCgK3iK5t" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --F6DilIiYCgK3iK5t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2023 at 09:53:32AM +0200, Laurenz Albe wrote: > On Mon, 2023-07-17 at 05:03 +0000, PG Bug reporting form wrote: >> Scenario is like, there was checkpoint operation failures going on the DB >> server since last 8 hours which means no successful checkpoint happened = in >> the DB server since last 8 hours. Then DB server went into the crash mode >> due to the exhausted disk space and did not came up as part of crash >> recovery. >=20 > Mistake #1: you did not monitor disk space. max_wal_size is a very critical piece to adjust. It is usually recommended to split pg_wal/ into its own partition so as the space allocated for WAL records is predictable across checkpoints. This is not a perfect science as max_wal_size is a soft limit so usually one needs an extra margin with a WAL partition. There have been some patches floating around to make that a hard limit, as well, but I don't think we've ever agreed on the semantics that would be acceptable when reaching the upper limit authorized. -- Michael --F6DilIiYCgK3iK5t Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmS09ncACgkQnvQgOdby QH1NIg//V6NAOLdBFWHyIGWklmzY7o95mgax5kOqMcuk4HV73iVq7QVnKci3+UTn uRBaf1hmzQOg/CGnQAd2Cf3UCqkJmQcEB/u6i7FRjSdH2B3QalvVOClIswyeYdYO kcFgTzAEUZpzcdXVzNY67JcFsAcYZmIqLSJfgZx7Vsfm6snBG5JMkFS9EWIxLpYp WkKfvEtnTzYIi1MubIZjXpWDSkeOfF+QgYtf5gK1ATy87+ZuDQr3XQfhZTxOzRG3 wgP9ZlUC/FIvOfbAPDCjK2FdugCAR31GSr9dFqWc6F4bqMIEawdZj62TxoEj0I0b sZmLyd8sULHn1jpuYCfCoFd0EaTFR56fovIGulyYQEQUNFfE2dDflv4RRbIpW4nD LmLD4vtA5Hq9yhPGeYdEh//UrGg2R7/CDFQrTG6mSxPVYvNakTnOtBQDHydThd0z fCttlPJWS1oySjBa1Kj37Z2katZYKjh66BIMVQqLp0DPLbdzaP1na0z6ceEJBE1l iyxpoGI7gfLFk//jx6pKSSgMSBuLq3WUE6bRGwbzTDp6uCNcDukvZ9i0si+fN1mL c4VmKQvBk2J6VdNKn7N/T6/pGvg7PcC6an8haCsudzX5FImgiZt6w2RoSE4lB9md 3M1K1ScoP1AZiJtQ5dY1Xyyz7v+wg0NFtHIUoawlN7vkHbjXXr0= =2sAY -----END PGP SIGNATURE----- --F6DilIiYCgK3iK5t--