Side effect of synchronous_commit = off

From: Yan Cheng CHEOK <yccheok(at)yahoo(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Side effect of synchronous_commit = off
Date: 2010-03-25 07:49:52
Message-ID: 856369.90827.qm@web65703.mail.ac4.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian von Bidder 2010-03-25 07:56:51 Re: Revoking CREATE TABLE
Previous Message Pavel Stehule 2010-03-25 07:34:09 Re: find a string contained in an attribute