Re: Postgresql TPS Bottleneck
От
MichaelDBA
Тема
Re: Postgresql TPS Bottleneck
Дата
Msg-id
97bb1892-4f54-9410-77bc-f8cd93f779a3@sqlexec.com
Ответ на
Список
Дерево обсуждения
Postgresql TPS Bottleneck <wakandavision@outlook.com>
Re: Postgresql TPS Bottleneck Mladen Gogala <gogala.mladen@gmail.com>
Re: Postgresql TPS Bottleneck MichaelDBA <MichaelDBA@sqlexec.com>
Re: Postgresql TPS Bottleneck Tomas Vondra <tomas.vondra@enterprisedb.com>
Re: Postgresql TPS Bottleneck <wakandavision@outlook.com>
Re: Postgresql TPS Bottleneck Jeff Janes <jeff.janes@gmail.com>
Re: Postgresql TPS Bottleneck <wakandavision@outlook.com>
Re: Postgresql TPS Bottleneck Benedict Holland <benedict.m.holland@gmail.com>
While setting these 2 parameters to off will make things go faster (especially for fsync), it is unrealistic to have these settings in a production environment, especiall fsync=off. You might get by with synchronous_commit=off, but with fsync=off you could end up with corruption in your database. synchronous_commit may not make anything go faster just change where the time is being spent. Regards, Michael Vitale wakandavision@outlook.com wrote on 3/31/2022 7:50 AM: > fsync = off > synchronous_commit = off
В списке pgsql-performance по дате отправления
