| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | jayakumar s <kumardba27(dot)postgresql(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: DB wal file disabled --_Query |
| Date: | 2024-11-14 14:02:48 |
| Message-ID: | CAKFQuwae6qPjqCPeK+P_M5zSxJoCdmLUeNcXyD16=ueUrpewuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, November 14, 2024, jayakumar s <kumardba27(dot)postgresql(at)gmail(dot)com>
wrote:
>
> Archive mode is already disabled. If more wal files will generate fs also
> reached 100 percent based on application data load.
>
> As updated archive enabled or disabled. Will any state wall file that
> will be generate correct?
>
WAL files are removed once they are no longer needed by the system. If
they are not being removed you have an issue you need to debug to figure
out why they are staying around.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-11-14 14:40:00 | Re: work_mem RAM Accounting in PostgreSQL |
| Previous Message | Mark Phillips | 2024-11-14 12:04:00 | Re: Row level security policy |