| From: | Bryon Roché <kain(at)kain(dot)org> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to speed WAL apply in destination |
| Date: | 2022-12-11 21:18:06 |
| Message-ID: | FDCF3710-A2AA-4D39-ACEE-27B979A51878@kain.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On December 9, 2022 10:50:07 AM UTC, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>On Fri, 2022-12-09 at 08:47 +0000, Bryon Roché wrote:
>>
>> There are fsync parameters which can be set to off that may provide a modest speed increase, at the cost of removing crash safety.
>
>That is spectacularly bad advice.
It is situational advice, and depending on your application, not bad advice at all. It is certainly not something you want off by default, or even regularly.
In fact, the PostgreSQL 15 (and earlier) versions cover this in the documentation for the fsync and synchronous_commit parameters in section 20.5, including considerations involved in deciding when to use those arameters, along with further references in the documentation to cover more of the performance, synchronicity, and durability parameters, in detail.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | srinivas oguri | 2022-12-12 03:02:18 | Re: How to speed WAL apply in destination |
| Previous Message | Mladen Gogala | 2022-12-11 20:22:26 | Re: How to speed WAL apply in destination |