Filter:

Activity

20262025202420232022202120202019201820172016201520142013201220112010200920082007200620052004200320022001200019991998
DecJanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on April 06, 2005

Threads18 messages
2Started
0Replied in own
16Replied to othersin 8 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)Plan for relatively simple query seems to be very inefficientover 21 years ago
Replied (other)monitoring database activity on solarisover 21 years ago
Replied (other)Plan for relatively simple query seems to be very inefficientover 21 years ago
Replied (other)Big trouble with memory !!over 21 years ago
Replied (other)COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusionover 21 years ago
Replied (other)monitoring database activity on solarisover 21 years ago
Replied (other)Plan for relatively simple query seems to be very inefficientover 21 years ago
Replied (other)Plan for relatively simple query seems to be very inefficientover 21 years ago
Replied (other)lower functionover 21 years ago
Replied (other)Big trouble with memory !!over 21 years ago
Replied (other)Problems with Set Returning Functions (SRFs)over 21 years ago
Started threadpgsql: Remove test for NULL node in ExecProcNode().over 21 years ago
Replied (other)Plan for relatively simple query seems to be very inefficientover 21 years ago
Replied (other)very slow after a while...over 21 years ago
Replied (other)Big trouble with memory !!over 21 years ago
Replied (other)Big trouble with memory !!over 21 years ago
Replied (other)What encoding to use for this error?over 21 years ago
Started threadpgsql: Merge Resdom nodes into TargetEntry nodes to simplify code andover 21 years ago