| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | "Holtgrewe, Manuel" <manuel(dot)holtgrewe(at)bihealth(dot)de>, Luca Ferrari <fluca1978(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [ext] Re: Pointers towards identifying bulk import bottleneck (walwriter tuning?) |
| Date: | 2019-08-28 20:28:45 |
| Message-ID: | 194a33666ebd5b24f29385c8e29aef454697d992.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2019-08-28 20:37:34 | Re: wal_level logical for streaming replication |
| Previous Message | Alban Hertroys | 2019-08-28 20:19:28 | Re: Question about password character in ECPG's connection string |