Re: A few new options for CHECKPOINT

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Bernd Helmle <mailings(at)oopsware(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A few new options for CHECKPOINT
Date: 2020-12-04 23:21:23
Message-ID: CDA8E47D-83B8-4EEA-86DA-19C5AF1BE0B3@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/4/20, 1:47 PM, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> On the UI of this patch, you're proposing to add the option FAST. I'm
> not a fan of this option name and propose that (if we have it) we use
> the name SPREAD instead (defaults to false).
>
> Now we don't actually explain the term "spread" much in the documentation;
> we just say "the writes are spread". But it seems more natural to build
> on that adjective rather than "fast/slow".

Here is a version of the patch that uses SPREAD instead of FAST.

Nathan

Attachment Content-Type Size
v3-0001-Add-SPREAD-option-to-CHECKPOINT.patch application/octet-stream 10.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-12-04 23:32:39 Re: A few new options for CHECKPOINT
Previous Message Tom Lane 2020-12-04 22:21:12 Re: Removal of operator_precedence_warning