Re: pg_restore causing ENOSPACE on the WAL partition. Fundamental issue?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Dimitrios Apostolou <jimis(at)gmx(dot)net>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_restore causing ENOSPACE on the WAL partition. Fundamental issue?
Date: 2025-06-12 14:52:40
Message-ID: CAKFQuwb15hSo4Jie4o5NEpH7_6ZTbZyBYKG1eV7QnNExwDgvxQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, June 12, 2025, Dimitrios Apostolou <jimis(at)gmx(dot)net> wrote:

>
> Why can't walwriter just refuse to write anything above a certain limit,
> thus freezing all other writers until the checkpointer frees a chunk of WAL?

There may be performance reasons discouraging this, but more likely it’s
just a lack of awareness, or maybe an insufficient benefit/cost ratio to
volunteer to address this corner-case scenario.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-06-12 14:56:28 Re: Replace some %llu remnants in the tree
Previous Message Dimitrios Apostolou 2025-06-12 14:51:00 Re: [PATCH v2] parallel pg_restore: move offset-building phase to before forking