Sure, but now when transaction 1 is "committed", it isn't actually guaranteed to be there in the face of interruption. That's a big change to the default behavior...
There was always a gap between "write to disk" and fsync. Now it's a bit longer because we did some other stuff, but that gap was possible before, too.
We still don't tell people it's committed until the fsync returns.
toast0|11 months ago
There was always a gap between "write to disk" and fsync. Now it's a bit longer because we did some other stuff, but that gap was possible before, too.
We still don't tell people it's committed until the fsync returns.
marsovo|11 months ago
Otherwise, is the suggestion that there be an artificial delay to allow other transactions to piggyback before returning success on commit 1?
Should that be a default? (That was the context of this thread)