Re: Return of the pg_wal issue..

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