Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| config:all_you_never_wanted_to_know_about_file_saving [2013/05/06 20:44] – add proper title colombanw | config:all_you_never_wanted_to_know_about_file_saving [2019/05/28 05:20] – Emphasized that use_atomic_file_saving overrides use_gio_unsafe_file_saving vstepaniuk | ||
|---|---|---|---|
| Line 75: | Line 75: | ||
| Disadvantages: | Disadvantages: | ||
| - | * There is a long standing bug or design fault in the GIO library that deletes the temporary file from the non-atomic save if writing the data file fails. | + | * There is a [[https:// |
| * The non-atomic save copies data over the network three times (read and write to make the temporary file, write the output file) which can be slow on remote networks. | * The non-atomic save copies data over the network three times (read and write to make the temporary file, write the output file) which can be slow on remote networks. | ||
| * Uses twice the disk space. | * Uses twice the disk space. | ||
| Line 95: | Line 95: | ||
| Disadvantages: | Disadvantages: | ||
| - | * Only works if use_gio_unsafe_file_saving is in operation, remember use_atomic_file_saving overrides it. | + | * Only works if use_gio_unsafe_file_saving is in operation, |
| * Uses twice the disk space. | * Uses twice the disk space. | ||
| * Can be slow on remote filesystems as it may have to read and write data to create the backup if renaming fails. | * Can be slow on remote filesystems as it may have to read and write data to create the backup if renaming fails. | ||
