Re: [GENERAL] Side effect of synchronous_commit = off

2010-03-29 Thread Arthur Turrini
Being asynchronous, means that write-to-disk will be queued in kernel for later execution, ie, postgresql won't wait for its write confirmation, but they will occurr in a serial manner. On Thu, Mar 25, 2010 at 4:49 AM, Yan Cheng CHEOK wrote: > I was wondering whether setting synchronous_commit

Re: [GENERAL] Side effect of synchronous_commit = off

2010-03-25 Thread Guillaume Lelarge
Le 25/03/2010 08:49, Yan Cheng CHEOK a écrit : > 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

[GENERAL] Side effect of synchronous_commit = off

2010-03-25 Thread Yan Cheng CHEOK
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 "flush