@robertjpayne I want to clarify further here. I’m not sure, but it seems like you might be confusing Sync Gateway persisting to disk (which it is not intended to do) with Couchbase Server.
Sync Gateway is a stateless glue piece that manages replications. Some of the discussion in the thread is about persisting SG checkpoints. These are used to make replications more efficient, but I believe there’s no loss if they don’t happen (@adamf or @jens can you confirm?).
So Couchbase Server has a mechanism for ensuring you know you’ve written to disk, but it sounds like it’s not currently controllable from Sync Gateway. Jens’ last point was that this isn’t typically as much of an issue as it sounds because not only do you have writes to disk, you have redundancy in having a write also getting pushed to your backup nodes in a cluster.
If you’re sure you need a guarantee of a write to disk after you create a document via Sync Gateway, it sounds like this would be an enhancement request we’d have to look at (again, @adamf or @jens if you can confirm). Of course there are legitimate situations where that’s needed, but most don’t. (Meaning I’m not intending to be rude in questioning whether you absolutely need the guarantee, just that sometimes people realize it’s not a real requirement.)