From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | noah(at)leadboat(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PG 13 release notes, first draft |
Date: | 2020-05-14 02:40:52 |
Message-ID: | 20200514024052.GA8853@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)momjian(dot)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(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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-05-14 02:43:19 | Re: tablespace_map code cleanup |
Previous Message | Andy Fan | 2020-05-14 02:38:44 | Re: [PATCH] Keeps tracking the uniqueness with UniqueKey |