Re: Return of the pg_wal issue..
| От | Saul Perdomo |
|---|---|
| Тема | Re: Return of the pg_wal issue.. |
| Дата | |
| Msg-id | CAN3jBgGPTuGKUFU=7gvdzjfRfzHYv74NuCsVAQD+J9PhoERcVA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Return of the pg_wal issue.. (Adrian Klaver <adrian.klaver@aklaver.com>) |
| Ответы |
Re: Return of the pg_wal issue..
|
| Список | pgsql-general |
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 a.m. Adrian Klaver <adrian.klaver@aklaver.com> 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
В списке pgsql-general по дате отправления: