Date: Tue, 5 May 2020 13:45:37 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Message-ID: <20200505184537.GC28974@telsasoft.com>
References: <20200505031600.GB21752@momjian.us>
 <20200505164503.GY28974@telsasoft.com>
 <20200505171809.GF21185@momjian.us>
 <20200505175001.GA28974@telsasoft.com>
 <20200505181024.GG21185@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200505181024.GG21185@momjian.us>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

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().

-- 
Justin