Make toasty client thread-safe and implement toasty_wakeup

This commit is contained in:
2025-11-20 03:51:01 +01:00
parent 9b40edb56c
commit b0313ffcf8
7 changed files with 341 additions and 49 deletions
+1
View File
@@ -22,3 +22,4 @@
[ ] Check write() errors when appending WAL entries
[ ] When WAL entries are partially written, remove partial data and fail
[ ] Find a way to ensure listing operations of large directories are handled
[ ] What happens if a client adds a chunk such that the hash already exists in the system? The client doesn't know it exists already. Will this lead to over-replication?