Re: How to speed WAL apply in destination

From: SASIKUMAR Devaraj <sashikumard(at)yahoo(dot)com>
To: kain(at)kain(dot)org, 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-20 11:32:34
Message-ID: 573865124.1608666.1671535954355@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi all
Issue resolved after increasing memory. 

Sent from Yahoo Mail on Android

On Mon, Dec 12, 2022 at 5:09 PM, Bryon Roché<kain(at)kain(dot)org> wrote:

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.


In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Dhirendra Singh 2022-12-22 04:25:22 Facing issue with cert authentication
Previous Message Ron 2022-12-19 19:11:16 Re: Using pgadmin as an OAuth2 proxy for PostgreSQL