-
In the documentation:
This seems to mean software like litestream, which uses taking over the WAL file for backups, wouldn't work. I just wanted to confirm I'm correct about that, so I don't use those two pieces of software together! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 15 replies
-
Shared-memory WAL was merged with #71. The driver should be fully compatible with Litestream on Linux and macOS.
|
Beta Was this translation helpful? Give feedback.
-
https://github.com/maxpert/marmot is an alternative from Litestream that uses NATS for storage. you can easily get it going using embedded nats too: https://github.com/maxpert/marmot/blob/master/stream/embedded_nats.go Its using github.com/mattn/go-sqlite3: |
Beta Was this translation helpful? Give feedback.
-
As an update on this, I'm considering asynchronous replication based on a VFS and the LTX format instead. If an ecosystem of tools forms around LTX (against which I can target compatibility) that seems a much better bet. |
Beta Was this translation helpful? Give feedback.
-
will swing by and do thing one soon hopefully |
Beta Was this translation helpful? Give feedback.
-
Hey @ncruces Regarding OPEN_READONLY WAL, suggest checking the golang code in Marmot. It's pretty simple code. |
Beta Was this translation helpful? Give feedback.
Shared-memory WAL was merged with #71.
The driver should be fully compatible with Litestream on Linux and macOS.
Your intuition is correct: as things stand this driver is not compatible with Litestream.Supporting WAL in a way that enables (an external process like) Litestream to work is particularly hard.