Found it. Kubernetes cronjob task. > On Feb 27, 2024, at 11:22 AM, Alvaro Herrera <alvherre@xxxxxxxxxxxxxx> wrote: > > It could be autovacuum processing large tables that haven't been > processed in a long time, in emergency mode. This happens if you turn > it off and do nothing to substitute it. We have autovacuum on, and pretty well tuned. > Some backup tools implement parallel archiving of WAL files, which helps > you deal with massive accumulation of them. We'll get that in an upgrade we're getting ready to deploy. Ironically, it might have just hidden this problem ;-)
