Re: PG 13 release notes, first draft

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 13 release notes, first draft
Date: 2020-05-05 20:18:28
Message-ID: 20200505201828.GJ21185@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 5, 2020 at 01:45:37PM -0500, Justin Pryzby wrote:
> On Tue, May 05, 2020 at 02:10:24PM -0400, Bruce Momjian wrote:
> > > > > | This is controlled by GUC wal_skip_threshold.
> > > > > I think you should say that's a size threshold which determines which strategy
> > > > > to use (WAL or fsync).
> > > >
> > > > I went with:
> > > > The WAL write amount where this happens is controlled by wal_skip_threshold.
> > > >
> > > > They can use the doc link if they want more detail.
> > >
> > > I guess I would say "relations larger than wal_skip_threshold will be fsynced
> > > rather than copied to WAL"
> >
> > How is this?
> >
> > Relations larger than wal_skip_threshold will have their files fynsced
> > rather than writing their WAL records.
>
> I see I was too late, but:
>
> Fix typo (fynsc) and maybe add parens().

Ah, I was looking for fsync to fix that and could not find it. Now I
found it with that spelling, I ended up using "fsync'ed".

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

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-05-05 20:22:12 Re: PG 13 release notes, first draft
Previous Message Bruce Momjian 2020-05-05 20:16:29 Re: PG 13 release notes, first draft