Re: max_wal_size

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pluzanov(at)postgrespro(dot)ru, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: max_wal_size
Date: 2020-09-01 21:01:31
Message-ID: 20200901210131.GB13613@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Tue, Jun 2, 2020 at 11:42:01PM +0300, Pavel Luzanov wrote:
> Hello,
>
> On 02.06.2020 22:35, Bruce Momjian wrote:
> > On Thu, May 28, 2020 at 12:21:14PM +0300, p(dot)luzanov(at)postgrespro(dot)ru wrote:
> > > WAL |-----------|-----+-----|-----+-----|-----+----->
> > >
> > > a b c
> > > CP +-----+ +-----+ +-----+
> > > b e b e b e
> > >
> > > Checkpointer process for point A starts at a(b) and ends at a(e).
> > > At the end of the work, CP makes a WAL record(plus symbol on WAL line).
> > >
> > > Back to the max_wal_size description:
> > > "Maximum size to let the WAL grow to between automatic WAL checkpoints."
> > >
> > > As I understand now, this is true when we talk about the checkpoint as a
> > > process.
> > > "Maximum size to let the WAL grow to between a(b) and b(e), between b(b) and c
> > > (e), etc".
> > What if we say:
> >
> > "Maximum size to let the WAL grow during automatic WAL checkpoints."
> >
> > That highlights the "process" part.
> >
> Really, "during" is associated with the process, while "between" with
> points.
>
> If there is no objection, simple patch attached.

Applied to all supported versions, thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Eisentraut 2020-09-01 21:30:11 Re: Additional Chapter for Tutorial
Previous Message Bruce Momjian 2020-09-01 18:10:18 Re: Adding description about the random_page_cost and parallel_leader_participation