Peter Wilkinson
Peter Wilkinson
This is what we are using which takes a slightly different approach - buffer the polygon by the edge length of a hex at it's centroid and desired resolution so...
Some more interesting bits... That generation is not present any more on s3. I've checked and there aren't any lifecycle rules on the bucket that might be deleting the generation....
A little extra - it was over 36 hours on that generation, the db it is replicating is very much only written to during business hours.
Some _good_ news here... I was trying to restore the db to see how long it takes and ran into the same error: ``` cannot find max wal index for...
Thanks. I've reverted back to v0.3.4 and will try to restore regularly to see if it happens again.
I've just checked and got the restore error again on v0.3.4... This restore is on a Mac machine ``` ~/go/bin/litestream restore -v -config litestream.yml -o DB DB /Users/pfw/DB(s3): restoring snapshot...
Yes, it is a 1k page. This database has had a long life... the oldest records are dated 2003 I can't be sure then the database file itself would have...
I'll get that new version of the db sorted as soon as I can. Let me know if there is a test version of litestream you'd like me to use....
Hi Ben. I've found the issue and it was driver error, many apologies for the goose chase. What was happening was there was a misconfiguration on a separate machine that...
Agreed, that anything to deal with this user error could easily become over engineering. Something simple that might work could be to have the ```replicate``` create a directory with the...