| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Victor Sudakov <vas(at)sibptus(dot)ru> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WAL storage when archive_command='' |
| Date: | 2022-09-11 06:29:18 |
| Message-ID: | CAKFQuwar9r_jQeLYnSHpL1A_8k2kV+NhMDHfHVA862sDr-cC-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Friday, September 9, 2022, Victor Sudakov <vas(at)sibptus(dot)ru> wrote:
>
> I just want to make sure that unarchived WAL files are never ever
> deleted and there is no limit on the number or size of unarchived WAL
> files.
>
>
The docs clearly answer this IMO:
If archive_command is an empty string (the default) while archive_mode is
enabled, WAL archiving is temporarily disabled, but the server continues to
accumulate WAL segment files in the expectation that a command will soon be
provided.
Though I suppose I would argue to either remove the word temporarily or
describe under what conditions, besides putting in a non-empty string,
would re-enable it. Additionally, change disabled to suspended since that
doesn’t contravene the behavior of an enabled archive mode to never remove
WAL without a successful execution of a non-empty archive_command.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leandro Bugalho | 2022-09-11 06:30:21 | Re: WAL storage when archive_command='' |
| Previous Message | Leandro Bugalho | 2022-09-11 06:28:56 | Error when execute insert/update |