Re: Read consistency when using synchronous_commit=off

From: pshadangi <pshadangi(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Read consistency when using synchronous_commit=off
Date: 2019-01-16 08:27:40
Message-ID: CAA+OQsRsL8nchjg_kJmGBYrO4b5Ana12QgYhNB--BaBXz-nzSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)fastmail(dot)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.
>
>
>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2019-01-16 08:46:30 Re: Read consistency when using synchronous_commit=off
Previous Message Pavel Stehule 2019-01-16 05:50:56 Re: Oracke BLOB to Postgres BYTEA using ora2pg