ecton
commented
6 months ago It's hard to answer this because I don't want to over-promise when it comes to other people's data. I currently am unaware of any reason this cannot be used in any projects, but I don't consider it "battle-tested."
Just a few months ago, #14 was reported which was a data loss bug. There could be other bugs lurking, but I am hopeful there aren't. But, until I know that people are successfully using it and not experiencing any issues, it's hard for me to say it's production-ready.
The log format and methodology shouldn't need to change before a 1.0 release. When I last worked on this project, I was in the process of adding a filesystem abstraction that I could use to do more thorough testing such as simulating IO errors after writing X bytes and so forth. I still want to finish that project, but I've been prioritizing other projects that, frankly speaking, have already earned more in Github Sponsors than all of my time working on open source database crates combined :laughing:.
With all of that said, I would encourage you to try it out! I haven't abandoned this project and will try to quickly resolve any bugs found.
Thanks for your great work on this crate. Really like the API exposed by OkayWAL.
The README mentions that this crate isn't yet production-ready. Is that still the case? Would like to use this in one of the projects.