Re: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?) - Mailing list pgsql-general

From Laurenz Albe
Subject Re: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)
Date
Msg-id 6fae1020051d2de8646c724ba782229af8323e7a.camel@cybertec.at
Whole thread Raw
In response to RE: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)  ("Holtgrewe, Manuel" <manuel.holtgrewe@bihealth.de>)
Responses RE: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)
Re: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)
List 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




pgsql-general by date:

Previous
From: Simon Kissane
Date:
Subject: Re: cannot CREATE INDEX because it has pending trigger events
Next
From: Ron
Date:
Subject: Re: Work hours?