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 194a33666ebd5b24f29385c8e29aef454697d992.camel@cybertec.at
обсуждение исходный текст
Ответ на Re: [ext] Re: Pointers towards identifying bulk import bottleneck(walwriter tuning?)  (Michael Lewis <mlewis@entrata.com>)
Список pgsql-general
On Wed, 2019-08-28 at 12:27 -0600, Michael Lewis wrote:
> > 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?

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?

In my experience, the performance will be almost as good as
with fsync=off, which is as good as it gets.

For an exact answer for your specific system, run a simple benchmark.

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




В списке pgsql-general по дате отправления:

Предыдущее
От: Alban Hertroys
Дата:
Сообщение: Re: Question about password character in ECPG's connection string
Следующее
От: Laurenz Albe
Дата:
Сообщение: Re: wal_level logical for streaming replication