forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit1420617
committed
Change client-side fsync_fname() to report errors fatally
Given all we have learned about fsync() error handling in the last fewyears, reporting an fsync() error non-fatally is not useful,unless you don't care much about the file, in which case you probablydon't need to use fsync() in the first place.Change fsync_fname() and durable_rename() to exit(1) on fsync() errorsother than those that we specifically chose to ignore.This affects initdb, pg_basebackup, pg_checksums, pg_dump, pg_dumpall,and pg_rewind.Reviewed-by: Michael Paquier <michael@paquier.xyz>Discussion:https://www.postgresql.org/message-id/flat/d239d1bd-aef0-ca7c-dc0a-da14bdcf0392%402ndquadrant.com1 parenta91e2fa commit1420617
1 file changed
+6
-8
lines changedLines changed: 6 additions & 8 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
51 | 51 |
| |
52 | 52 |
| |
53 | 53 |
| |
54 |
| - | |
55 |
| - | |
56 | 54 |
| |
57 | 55 |
| |
58 | 56 |
| |
| |||
250 | 248 |
| |
251 | 249 |
| |
252 | 250 |
| |
253 |
| - | |
254 |
| - | |
| 251 | + | |
| 252 | + | |
255 | 253 |
| |
256 | 254 |
| |
257 | 255 |
| |
| |||
294 | 292 |
| |
295 | 293 |
| |
296 | 294 |
| |
297 |
| - | |
| 295 | + | |
298 | 296 |
| |
299 |
| - | |
| 297 | + | |
300 | 298 |
| |
301 | 299 |
| |
302 | 300 |
| |
| |||
364 | 362 |
| |
365 | 363 |
| |
366 | 364 |
| |
367 |
| - | |
| 365 | + | |
368 | 366 |
| |
369 |
| - | |
| 367 | + | |
370 | 368 |
| |
371 | 369 |
| |
372 | 370 |
| |
|
0 commit comments
Comments
(0)