Filter:

Activity

20262025202420232022202120202019201820172016201520142013201220112010200920082007200620052004200320022001200019991998
JanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on January 29, 2007

Threads18 messages
4Started
1Replied in own
13Replied to othersin 7 threads
Patchesof which 2 carried a patch
0New patchfirst in its thread
2Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)Re: Predicted lifespan of different PostgreSQLbranchesover 19 years ago
Replied (other)PostgreSQL 9.0over 19 years ago
Replied (other)Predicted lifespan of different PostgreSQL branchesover 19 years ago
Replied (other)psql possible TODOover 19 years ago
Replied (other)psql possible TODOover 19 years ago
Replied (other)Follow-up patch14.4 If You Are Upgrading - Suggested Improvementsover 19 years ago
Started threadpgsql: Update wording for minor release upgrades, per Alvaro.over 19 years ago
Replied (other)Modifying and solidifying contribover 19 years ago
Replied (other)Modifying and solidifying contribover 19 years ago
Started threadpgsql: Done: < * Add Globally/Universally Unique Identifier (GUID/UUID)over 19 years ago
Replied (other)Modifying and solidifying contribover 19 years ago
Replied (other)Predicted lifespan of different PostgreSQL branchesover 19 years ago
Replied (other)FW: Possible to emulate pre-8.2 behaviour of SET CONSTRAINTS?over 19 years ago
Replied (other)Modifying and solidifying contribover 19 years ago
Started threadpgsql: Use sizeof() for snprintf() buffer length.over 19 years ago
Replied (other)Follow-up patchFW: Possible to emulate pre-8.2 behaviour of SET CONSTRAINTS?over 19 years ago
Started threadpgsql: Update process termination message to display signal number andover 19 years ago
Replied (own)Recursive query syntax ambiguityover 19 years ago