Messages in week 16 (Apr 16 - Apr 22, 2018)
8 messages0 started threads0 replied (own)8 replied (other)1 other threads0 first patch1 follow-up patch
| Activity | Thread | Sent |
|---|---|---|
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other)Follow-up patch | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |
| Replied (other) | PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS | about 8 years ago |