Messages in week 16 (Apr 16 - Apr 22, 2018)
Threads8 messages
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
| Activity | Thread | Sent |
|---|---|---|
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | over 8 years ago |