Search Postgresql Archives

Side effect of synchronous_commit = off

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

 



I was wondering whether setting synchronous_commit = off will have the following side effect.

(1) Process A issues UPDATE command on row x, from false to true.
(2) After that, Process B READ from row x.

Is it possible that when Process B start to read row x, the "true" value is not being "flushed" to the table. Hence, process B will read the row x as false?

If this situation will happen, is it possible that Process B may issues a command, use to "flush all" pending data to be written to disk?

Thanks and Regards
Yan Cheng CHEOK


      


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[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