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 1mFd8I-0006rB-5u for pgsql-admin@arkaria.postgresql.org; Mon, 16 Aug 2021 13:58:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mFd8H-0004o9-1c for pgsql-admin@arkaria.postgresql.org; Mon, 16 Aug 2021 13:58:29 +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 1mFd8G-0004o1-P5 for pgsql-admin@lists.postgresql.org; Mon, 16 Aug 2021 13:58:28 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mFd8D-0008OL-KA for pgsql-admin@lists.postgresql.org; Mon, 16 Aug 2021 13:58:28 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 2694788D55 for ; Mon, 16 Aug 2021 13:58:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at emo01-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo01-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYwFMygKSGqL for ; Mon, 16 Aug 2021 13:58:19 +0000 (UTC) Received: from smtpclient.apple (unknown [4.28.96.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 0008188D4E for ; Mon, 16 Aug 2021 13:58:18 +0000 (UTC) From: Scott Ribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) Subject: max_slot_wal_keep_size Message-Id: <58D79C5B-B9FE-403B-97C0-40B6DF1E00CF@elevated-dev.com> Date: Mon, 16 Aug 2021 07:58:17 -0600 To: Pgsql-admin X-Mailer: Apple Mail (2.3654.100.0.2.22) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk If I use max_slot_wal_keep_size to limit disk impact of a down replica, = and subsequently a down replica causes PG to hit this limit, is there a = particular message that will be logged when the limit is crossed and PG = starts to purge WAL? Context is: trying to debug a failure to bring up a replica, where the = failure happened in the middle of a moderately complex chain of events = that likely started with a bad disk. (Patroni is involved, FWIW) -- Scott Ribe scott_ribe@elevated-dev.com https://www.linkedin.com/in/scottribe/ -- Scott Ribe scott_ribe@elevated-dev.com https://www.linkedin.com/in/scottribe/