| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Naveen Sankineni <nsankineni(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Commit Delay |
| Date: | 2020-04-30 23:33:54 |
| Message-ID: | 20200430233354.GB31272@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vinod kale | 2020-05-01 04:18:10 | Postgres pgbackrest issue. |
| Previous Message | Naveen Sankineni | 2020-04-30 23:31:01 | Commit Delay |