Filter:

Activity

20262025202420232022202120202019201820172016201520142013201220112010200920082007200620052004200320022001200019991998
JanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on April 04, 2018

Threads15 messages
6Started
0Replied in own
9Replied to othersin 3 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)PgUpgrade bumped my XIDs by ~50M?over 8 years ago
Replied (other)Dead link in ltree documentationover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 8 years ago
Started threadpgsql: docs: update ltree URL for the DMOZ catalogover 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