Re: Read consistency when using synchronous_commit=off - Mailing list pgsql-general

From pshadangi
Subject Re: Read consistency when using synchronous_commit=off
Date
Msg-id CAA+OQsRsL8nchjg_kJmGBYrO4b5Ana12QgYhNB--BaBXz-nzSQ@mail.gmail.com
Whole thread Raw
In response to Re: Read consistency when using synchronous_commit=off  (Ravi Krishna <srkrishna@fastmail.com>)
Responses Re: Read consistency when using synchronous_commit=off  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
Thanks Ravi for the clarification, we will go ahead with "synchronous_commit=off".

On Wed, Jan 16, 2019 at 10:47 AM Ravi Krishna <srkrishna@fastmail.com> wrote:
Sorry I misunderstood.  The term "read consistency" is generally used either in the context of isolation level or in the context of slaves.

We don't have standby instance, as I have mentioned we are using just one instance of postgres serving local clients running on the same machine, do you know in this case what is the behavior ?


You are good.  All transactions update buffer cache too, along with WAL buffer and hence other sessions can immediately see the changes. synchronous_commit=off will only reduce the fsync calls, which makes them less crash safe, but the database consistency is not compromised.
  



pgsql-general by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Oracke BLOB to Postgres BYTEA using ora2pg
Next
From: Ron
Date:
Subject: Re: Read consistency when using synchronous_commit=off