| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Koen De Groote <kdg(dot)dev(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Reasons for not overwriting processed wal archives? |
| Date: | 2022-05-18 21:18:16 |
| Message-ID: | CAKFQuwY0akhPwvEc5rbYyR_kh89vjm0PkVnsWCHbCD9WGghRig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, May 18, 2022, Koen De Groote <kdg(dot)dev(at)gmail(dot)com> wrote:
> The documentation here: https://www.postgresql.org/
> docs/11/continuous-archiving.html
>
> States:
>
> > It is advisable to test your proposed archive command to ensure that it
> indeed does not overwrite an existing file, *and that it returns nonzero
> status in this case*.
>
> Why exactly is this?
>
Newer doc versions also say:
This is an important safety feature to preserve the integrity of your
archive in case of administrator error (such as sending the output of two
different servers to the same archive directory).
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2022-05-18 21:59:23 | Re: Who am I? Where am I connected? |
| Previous Message | Koen De Groote | 2022-05-18 21:08:17 | Reasons for not overwriting processed wal archives? |