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 1tazk1-0072LL-IO for pgsql-general@arkaria.postgresql.org; Thu, 23 Jan 2025 16:07: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 1tazk0-000Fom-0P for pgsql-general@arkaria.postgresql.org; Thu, 23 Jan 2025 16:07:36 +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 1tazjy-000Fod-EJ for pgsql-general@lists.postgresql.org; Thu, 23 Jan 2025 16:07:35 +0000 Received: from fout-b8-smtp.messagingengine.com ([202.12.124.151]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tazju-00177L-0Y for pgsql-general@postgresql.org; Thu, 23 Jan 2025 16:07:34 +0000 Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfout.stl.internal (Postfix) with ESMTP id 0AE1A1140103; Thu, 23 Jan 2025 11:07:28 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Thu, 23 Jan 2025 11:07:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding: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=fm2; t=1737648447; x=1737734847; bh=ndVnu2IrvT14CXnW20Gws8ZvfCWTA8kWKr2pefad7W0=; b= eIpUMBUXSHWeVRSOcaay5XIcKjln45Xf5u2gpDStArAkIBUSogH2STik38iCx3OX qf12hDflgTfIRNyZjWqrAShjWx1dYaQLsKlaxKXBlCO26PQ0t4tJ7HMJtRbuketd cWCD5PXjqBMkYE5pwOGHsg0kNkPROWuMqGy1si0dZvsPno0Nwo1WwEVuSvMfUArq Qmfyli+b67rTdbdo1lGhZqckOet5gfFOw3l0aa1kyF8TExXFyECcxGjDdhZ8ua3D gZrnw9rJcegzVnJXbcwjdAWU/m8/0wVfzeEpwSQZLd0KzjamkND5poO95I9OO+vZ iCK3BDMpXJc3shchBrmDVw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=fm3; t=1737648447; x= 1737734847; bh=ndVnu2IrvT14CXnW20Gws8ZvfCWTA8kWKr2pefad7W0=; b=k MAj22xwYOLJtoELph/EtSe4J4eJLgOUDYlsy6FFeFZ1kKrf0fqAlbYfRd04yGwhy WA652T9By5AtPWC8uuFdC2S38x6pL54XdxDSKV57LIrZ8G7bcnfnx61gbDMdRsoM Bj4WTJDY72AbUi8BKOkQKMAVq887bYaIEmSQtDmYHKegR0sANXKIzA09epM2btD3 Xk+pSOn3T4p5IAa+2xYLepPLAgHhZb5EXoMof20fv4m50qUDoneBZMEsnfb9Z4As qpmiAF5mo6uOxNpuB5M6IESECaZoJGbbXtSujS+SnQwtLwgUA4uP9OhN21Q1dPE0 r6bTZFtE9SmtirOLXPxfA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrudejgedgvddutdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddv jeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpefgudefkefhveefleev ieeuveehvdduudekuddvvdelhfeuueeijedtuedvvedvueenucffohhmrghinhepphhosh htghhrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnh gspghrtghpthhtohepfedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepshgruhhl rdhpvghrughomhhosehgmhgrihhlrdgtohhmpdhrtghpthhtohepphgruhhlsghrihhnug hushgrkeeksehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgr lhesphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 23 Jan 2025 11:07:27 -0500 (EST) Message-ID: Date: Thu, 23 Jan 2025 08:07:26 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Return of the pg_wal issue.. To: Saul Perdomo , Paul Brindusa Cc: pgsql-general References: <0ba329ef-62aa-4ab3-aefd-141baabced3b@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/23/25 06:51, Saul Perdomo wrote: > This is why everybody will tell you "don't just delete these files, > archive them properly!" Again, for operational purposes, you could just > delete them. But you really want to make a /copy /of them before you > do... you know, /just in case /something bad happens to your DB that > makes you want to roll it back in time. No you can't just delete them for operational purposes without knowledge of whether they are still needed or not. Per: https://www.postgresql.org/docs/current/wal-intro.html and https://www.postgresql.org/docs/current/wal-configuration.html Short version, a WAL file must remain until a checkpoint is done that makes it's content no longer needed. > Cheers > Saul > -- Adrian Klaver adrian.klaver@aklaver.com