mirror of
https://github.com/KumoCorp/kumomta.git
synced 2026-08-19 16:01:08 +00:00
Wez Furlong
42bf5c5e61
We've been hoping that mkdocs-material will ship the much anticipated search enhancements for some time, but it's time to recognize that we need to do something to improve the search results with how things work right now. This is a big commit that changes the titles of the various pages from the code-annotated synopsis to just the name of the function. This makes it much easier now to match things like `kumo.reject` directly, but `reject` remains awkward to find. I think this is the best that we can do at this time. A few functions have been annotated with the `status: deprecated` to show as deprecated in the toc/nav (shows with a little trash can next to the name).
18 lines
603 B
Markdown
18 lines
603 B
Markdown
# set_force_sync
|
|
|
|
```lua
|
|
message:set_force_sync(force)
|
|
```
|
|
|
|
When `force` is `true`, each future attempt to save the message metadata or
|
|
data will use a high durability write, delaying further processing until the
|
|
message data has been written to the spool.
|
|
|
|
When `force` is `false`, which is the default setting, whether high durability
|
|
writes are used is a function of the configuration of the spool(s) that you
|
|
have enabled in your configuration.
|
|
|
|
!!! note
|
|
Using this together with RocksDB spool can be incredibly harmful to overall
|
|
performance, as forcing a flush is a database-wide operation.
|