pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: noah@leadboat.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: PG 13 release notes, first draft
Date: Wed, 13 May 2020 22:40:52 -0400
Message-ID: <20200514024052.GA8853@momjian.us> (raw)
In-Reply-To: <20200514.095141.1411370156366955955.horikyota.ntt@gmail.com>
References: <20200512203809.GA4666@momjian.us>
	<20200513.115633.157251733478541458.horikyota.ntt@gmail.com>
	<20200513151518.GA20111@momjian.us>
	<20200514.095141.1411370156366955955.horikyota.ntt@gmail.com>

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 +





view thread (194+ messages)  latest in thread

Message-ID: <20200514024052.GA8853@momjian.us>
Permalink:  ../20200514024052.GA8853@momjian.us/
Also on:    postgresql.org/message-id/20200514024052.GA8853@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, horikyota.ntt@gmail.com, noah@leadboat.com
  Subject: Re: PG 13 release notes, first draft
  In-Reply-To: <20200514024052.GA8853@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox