Filter:

Activity

20262025202420232022202120202019201820172016201520142013201220112010200920082007200620052004200320022001200019991998
JanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on January 16, 2001

Threads16 messages
5Started
2Replied in own
9Replied to othersin 7 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)postgres 7.0.3 core dumpsover 25 years ago
Replied (other)Waiting for postmaster to be completely startedover 25 years ago
Replied (other)Unknown Type 'ame' [urgent]over 25 years ago
Started threadpgsql/src/backend/catalog genbki.shover 25 years ago
Replied (other)RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad ideaover 25 years ago
Started threadDeadLockCheck is buggyover 25 years ago
Replied (other)Re: INIT DB FAILUREover 25 years ago
Replied (other)RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad ideaover 25 years ago
Started threadpgsql/src include/storage/proc.h backend/stora ...over 25 years ago
Replied (other)Performance degradation in PostgreSQL 7.1beta3 vs 6.5.3over 25 years ago
Replied (other)INIT DB FAILUREover 25 years ago
Replied (other)RE: SIGTERM -> elog(FATAL) -> proc_exit() is probably a bad ideaover 25 years ago
Started threadpgsql/src include/storage/lock.h include/stora ...over 25 years ago
Replied (own)Why is LockClassinfoForUpdate()'s mark4update a good idea?over 25 years ago
Started threadRe: Spot the error in my plpgsql...over 25 years ago
Replied (own)Why is LockClassinfoForUpdate()'s mark4update a good idea?over 25 years ago