Re: Writing WAL files

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Robert Inder <robert(at)interactive(dot)co(dot)uk>
Cc: Michael Lewis <mlewis(at)entrata(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Writing WAL files
Date: 2020-10-05 19:33:24
Message-ID: CAKFQuwY1g92Hz6RXBuYa4snMTY09ZfHwktBQi+Z+gXcfH3Zt9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday, October 5, 2020, Robert Inder <robert(at)interactive(dot)co(dot)uk> wrote:

> But the change Adrian Klaverd highlighted suggests that this is
> deliberately no longer the case,
> and I am left wondering what it does, in fact do/mean now.
>

“If no WAL has been written since the previous checkpoint, new checkpoints
will be skipped even if checkpoint_timeout has passed. ‘

https://www.postgresql.org/docs/13/wal-configuration.html

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-10-05 19:34:35 Re: UUID generation problem
Previous Message James B. Byrne 2020-10-05 19:30:01 Re: UUID generation problem