Search Postgresql Archives

Re: Read consistency when using synchronous_commit=off

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




A crash-unsafe database is for data you don't care about.


On 1/16/19 2:27 AM, pshadangi wrote:
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@xxxxxxxxxxxx> 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.
  


--
Angular momentum makes the world go 'round.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux