On Thu, May 14, 2020 at 09:51:41AM +0900, Kyotaro Horiguchi wrote:
> At Wed, 13 May 2020 11:15:18 -0400, Bruce Momjian <bruce@momjian.us> wrote in
> > On Wed, May 13, 2020 at 11:56:33AM +0900, Kyotaro Horiguchi wrote:
> It is just an more accurate (not an detailed) version of the
> previously proposed description. If we simplify that, I choose to
> remove explanation on wal_skip_threshold.
>
> How about this?
>
> WAL-logging is now skipped while all kinds of bulk-insertion, then
> relations are sync'ed to disk at commit. Previously this was done
> only for COPY operations, but the implementation had a bug that could
> cause data loss during crash recovery.
OK, I went with this text, stating WAL "generation" is skipped:
Allow skipping of WAL for full table writes if wal_level is 'minimal'
(Kyotaro Horiguchi)
Relations larger than wal_skip_threshold will have their files
fsync'ed rather than generating WAL. Previously this was done
only for COPY operations, but the implementation had a bug that
could cause data loss during crash recovery.
--
Bruce Momjian <bruce@momjian.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 +