| From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
|---|---|
| To: | wakandavision(at)outlook(dot)com |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgresql TPS Bottleneck |
| Date: | 2022-03-31 18:55:00 |
| Message-ID: | 97bb1892-4f54-9410-77bc-f8cd93f779a3@sqlexec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)outlook(dot)com wrote on 3/31/2022 7:50 AM:
> fsync = off
> synchronous_commit = off
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2022-03-31 19:16:50 | Re: Postgresql TPS Bottleneck |
| Previous Message | Mladen Gogala | 2022-03-31 14:44:57 | Re: HIGH IO and Less CPU utilization |