| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| 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 18:27:51 |
| Message-ID: | CAHOFxGqmM5i_z_urcFGoAq0tTd4MVQ+wGNyinWzN1USmQVxQWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 27, 2019 at 9:45 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> 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.
It seems like it depends on your definition of crash-safe. Data loss can
occur but not data corruption, 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | francis picabia | 2019-08-28 18:36:00 | Re: How to log 'user time' in postgres logs |
| Previous Message | Vijaykumar Jain | 2019-08-28 16:14:24 | wal_level logical for streaming replication |