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

Поиск
Список
Период
Сортировка
От Laurenz Albe
Тема Re: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)
Дата
Msg-id 6fae1020051d2de8646c724ba782229af8323e7a.camel@cybertec.at
обсуждение исходный текст
Ответ на RE: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)  ("Holtgrewe, Manuel" <manuel.holtgrewe@bihealth.de>)
Ответы RE: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)  ("Holtgrewe, Manuel" <manuel.holtgrewe@bihealth.de>)
Re: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)  (Michael Lewis <mlewis@entrata.com>)
Список 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 по дате отправления:

Предыдущее
От: Simon Kissane
Дата:
Сообщение: Re: cannot CREATE INDEX because it has pending trigger events
Следующее
От: Ron
Дата:
Сообщение: Re: Work hours?