Re: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?)

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: "Holtgrewe, Manuel" <manuel(dot)holtgrewe(at)bihealth(dot)de>, Luca Ferrari <fluca1978(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?)
Date: 2019-08-28 03:45:43
Message-ID: 6fae1020051d2de8646c724ba782229af8323e7a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Holtgrewe, Manuel wrote:
> Switching off fsync leads to a drastic time improvement but still
> higher wall-clock time for four threads.

Don't do that unless you are ready to start from scratch with a new
"initdb" in the case of a crash.

You can do almost as good by setting "synchronous_commit = off",
and that is crash-safe.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2019-08-28 04:56:27 Re: Work hours?
Previous Message Simon Kissane 2019-08-28 03:38:52 Re: cannot CREATE INDEX because it has pending trigger events