Filter:

Activity

2026202520242023202220212020201920182017201620152014201320122011201020092008
JanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on April 09, 2018

Threads12 messages
0Started
0Replied in own
12Replied to othersin 3 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)Optional message to user when terminating/cancelling backendover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)Verbosity of genbki.plover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago
Replied (other)PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFSover 8 years ago