Re: Commit Delay - Mailing list pgsql-admin

From Bruce Momjian
Subject Re: Commit Delay
Date
Msg-id 20200430233354.GB31272@momjian.us
Whole thread Raw
In response to Commit Delay  (Naveen Sankineni <nsankineni@gmail.com>)
Responses RE: Commit Delay  ("Thawley, Peter" <pthawley@amazon.com>)
List pgsql-admin
On Thu, Apr 30, 2020 at 07:31:01PM -0400, Naveen Sankineni wrote:
> Hello ,
> 
> I would need your advice on which parameter is least impacted in terms of Data
> Loss if we wanted to set .
> One of our Database is waiting on I/O when there is a batch operation that runs
> to Insert/Delete table data is impacting the small updates that runs  on a
> continuous basis where it shows that wait is on walwritelock.
> 
> commit_delay 
> synchronous_commit

The full list is here:

    https://www.postgresql.org/docs/12/non-durability.html

I would say synchronous_commit.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-admin by date:

Previous
From: Naveen Sankineni
Date:
Subject: Commit Delay
Next
From: vinod kale
Date:
Subject: Postgres pgbackrest issue.