| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Rui DeSousa <rui(at)crazybean(dot)net> |
| Cc: | pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: q re removal/recycling of WAL files |
| Date: | 2021-11-04 00:57:18 |
| Message-ID: | D1A01608-4D0A-4AD5-BAB0-980B7B68FE7A@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Nov 3, 2021, at 5:37 PM, Rui DeSousa <rui(at)crazybean(dot)net> wrote:
>
> WAL file can’t be recycled until it is no longer needed; thus after a checkpoint and archived as well (if enabled).
Ah yes, that's it! We are archiving WAL, and I imagine what happened easily outran the pace of archiving.
There was an exponential backoff between the retries, so although I could imagine rapid-fire retries filling disk with WAL before checkpoint running, I was having a little doubt about that happening in this case. I'm sure it was the archiving.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Denninger | 2021-11-04 13:21:30 | Re: Encoding error during database restore |
| Previous Message | Laurenz Albe | 2021-11-03 23:38:12 | Re: q re removal/recycling of WAL files |