title: Is there a delay before other transactions see a commit if using asynchronous commit in Postgresql?
body: <p>I'm looking into optimizing throughput in a Java application that frequently (100+ transactions/second) updates data in a Postgresql database. Since I don't mind losing a few transactions if the database crashes, I think that using <strong>asynchronous commit</strong> could be a good fit.</p>
  
  <p>My only concern is that I don't want a delay after commit until other transactions/queries see my commit. I am using the default isolation level "Read committed".</p>
  
  <p>So my question is: Does using <strong>asynchronous commit</strong> in Postgresql in any way mean that there will be delays before other transactions see my committed data or before they proceed if they have been waiting for my transaction to complete? (As mentioned before, I don't care if there is a delay before my data is persisted to disk.)</p>