3 ms·

It just breaks the transaction guarantee. In most cases, you don't want it. In other cases, like logging, pipeline mode may be better suited.

• ddorian43 2y ago
  No? Can you explain? It breaks the durabality for that transaction until a new transaction with synchronous commit 'on' completes or time passes for auto-fsync.
  • feverzsj 2y ago
    On client side, there is no explicit way to know which transaction is broken when there are multiple transactions undergoing. If your use case relies on transactional assumption, it may fail at some point.
    • ddorian43 2y ago
      On client side you know because you're setting the async-commit on a case basis. All transactions work the same. When/If the server fails, some transactions (that you allowed yourself) may be not durable (or not replicated). But all things are still transactional.
    • deleted 2y ago
      [deleted]