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 1tb2TG-007Rp9-Cs for pgsql-general@arkaria.postgresql.org; Thu, 23 Jan 2025 19:02:30 +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 1tb2TF-002gly-5h for pgsql-general@arkaria.postgresql.org; Thu, 23 Jan 2025 19:02:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tb2TE-002glq-Re for pgsql-general@lists.postgresql.org; Thu, 23 Jan 2025 19:02:28 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tb2TC-0018o9-23 for pgsql-general@postgresql.org; Thu, 23 Jan 2025 19:02:27 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-303548a9361so10294941fa.0 for ; Thu, 23 Jan 2025 11:02:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737658945; x=1738263745; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HlGAJGcqe0SPRiVVjn4ALYt+AzpGJYthbeFbbT9cu7g=; b=eDMifBrzopuRa0ZSGmYdMZr/3aM6jh5wsBwqlssA2URHrfJv5rkqJSb9Dod1dd1yfY jQGk9ON604qg+iwTF62z7TwqRnEqZUmPF2jjF1AhUSkp6OYTAh4Rc8D46A2tJhzhJC0E qDxVsUEoiHh2M5LXGD5d0DUOmkhztOzNym/8VT9tnZbHIXg7BiXw0hAmuxq6fR1RnJpE aVLyFVKZe8+1Rb21xyc8zBGULPj2b4HReb6jCrv9yGGU4y3fm7UC32NbnjnqWOaFFk11 gEchglpEw/4F0bVsaJK3zFMjG23szg6pBYcrBjFgrWxX2rf+KQxz7pm/NrtMCP0UN7Rx ljpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737658945; x=1738263745; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HlGAJGcqe0SPRiVVjn4ALYt+AzpGJYthbeFbbT9cu7g=; b=MtTswKsbEaz+LNE3OVfH7r5AF0yegaM1pxYZNPgVQRRP5iDJbzujMduigZHrVflmFg koeVfwdzbtdv+p+9Nc0NCHi7X3WrQTlebqKRSEUGXiGO/0rKnAlshRYQCDuYfPF3lSLs DELzNYtFGtuiYsCDWpBvHFOfR1TcyxGqD6sVYjK2HMFmCO3YnF+Hq0GmV/8wVENrn6Ri dwt4r4ECq0zd9MchMNDODBrITYAAcRzWGPcrLaJQUX5JMfFbaziXsbMmIGRn1BNw1+Zt CCDaXJsRl+iPbZFkhe8T0r87DWhOs5Tt2tz8uOQx2q07NgBuAEI6WGENhtAUw9GaVZ9D 8ekQ== X-Forwarded-Encrypted: i=1; AJvYcCUWcWVcIS8axUmggXMBBcU9uDfCmP6YMdfW82OLR9ZYfKzEzIQHPQuyx3N/9i1FOsOzioKoe/RuB1leSQFH@postgresql.org X-Gm-Message-State: AOJu0YwQ9g+M9L+nKsTs/f92zxMjoVzsbxS1WrhDSbKaZwwkTe3o2Ha3 5WzI+m46SV6rl9X7UMXIr2HKr4aM6LRacTW1tmQ8BcJyCUcN8nF3wkmwz8Ot4pdr4xd6Zyn9PlL 02v7uzXeScaAeZeO6GGNx70UbTKk= X-Gm-Gg: ASbGnctIrEI0dJ+1y663lJ23ty/8eRGokbV8NwP+TBMCxTxVB9/m3LKNaejWb9J6zn+ 0bGOYsDabJmgN9lcvae6FIa2n+14lzxCEiWOO1ZFpcl3nwWkwqiaiMTivLFIr X-Google-Smtp-Source: AGHT+IFQGXs3kmnuB1qspsz7vmz8pmz45JjXYjiJ8JCZK5l9SAMWaIXG1A4R98EGp8qJ9o0lmp0maYTxYzEP70KU7h4= X-Received: by 2002:a2e:a374:0:b0:300:330d:a5c4 with SMTP id 38308e7fff4ca-3072ca694d1mr82382381fa.10.1737658943609; Thu, 23 Jan 2025 11:02:23 -0800 (PST) MIME-Version: 1.0 References: <0ba329ef-62aa-4ab3-aefd-141baabced3b@aklaver.com> In-Reply-To: From: Saul Perdomo Date: Thu, 23 Jan 2025 14:02:12 -0500 X-Gm-Features: AbW1kvY6NAeW31lKjZRxHpb1_eJlwcRzMEwdy4ER34YDchXLTjsMkvCNR8ovoMc Message-ID: Subject: Re: Return of the pg_wal issue.. To: Adrian Klaver Cc: Paul Brindusa , pgsql-general Content-Type: multipart/alternative; boundary="000000000000132824062c6440ff" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000132824062c6440ff Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the correction Adrian - my oversimplification went too far, and into "plain wrong" territory. (The detail that I felt was too much for this explanation was: "and the way to simply get rid of them would be to set your archive command to '/bin/true', say".. but didn't want to make it seem like I was suggesting Paul do that) On Thu, Jan 23, 2025, 11:07=E2=80=AFa.m. Adrian Klaver wrote: > 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 > > --000000000000132824062c6440ff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the correction Adrian - my oversimplification = went too far, and into "plain wrong" territory.
=
(The detail that I felt was too much for this e= xplanation was: "and the way to simply get rid of them would be to set= your archive command to '/bin/true', say".. but didn't wa= nt to make it seem like I was suggesting Paul do that)=C2=A0
On Thu, Jan 23, 2025, 11:07=E2=80=AFa.m. Adrian Klaver <adrian.klaver@aklaver.com>= wrote:
On 1/23/25 06:51, Saul Perd= omo wrote:

> This is why everybody will tell you "don't just delete these = files,
> archive them properly!" Again, for operational purposes, you coul= d just
> delete them. But you really want to make a /copy /of them before=C2=A0= you
> do... you know, /just in case /something bad happens to your DB that <= br> > makes you want to roll it back in time.

No you can't just delete them for operational purposes without knowledg= e
of whether they are still needed or not.

Per:

https://www.postgresql.org/docs/cur= rent/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

--000000000000132824062c6440ff--