On Tue, Aug 27, 2019 at 9:45 PM Laurenz Albe <laurenz.albe@xxxxxxxxxxx> wrote:
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.
It seems like it depends on your definition of crash-safe. Data loss can occur but not data corruption, right? Do you know any ballpark for how much difference in performance it makes to turn off synchronous_commit or what type of hardware or usage it would make the biggest (or least) difference?
