From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 13 release notes, first draft |
Date: | 2020-05-05 18:45:37 |
Message-ID: | 20200505184537.GC28974@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-05-05 18:48:58 | Re: WAL usage calculation patch |
Previous Message | Jeff Davis | 2020-05-05 18:44:33 | Re: PG 13 release notes, first draft |