Filter:

Activity

20262025202420232022202120202019201820172016201520142013201220112010200920082007200620052004200320022001200019991998
DecJanFebMarAprMayJunJulAugSepOctNovDec
Wk1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Messages on August 22, 2015

Threads16 messages
8Started
0Replied in own
8Replied to othersin 6 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)Error message with plpgsql CONTINUEabout 11 years ago
Replied (other)(full) Memory context dump considered harmfulabout 11 years ago
Replied (other)PostgreSQL Developer Best Practicesabout 11 years ago
Replied (other)PostgreSQL for VAX on NetBSD/OpenBSDabout 11 years ago
Replied (other)(full) Memory context dump considered harmfulabout 11 years ago
Replied (other)Converting char to varchar automaticallyabout 11 years ago
Replied (other)Memory allocation in spi_printtup()about 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Started threadpgsql: Avoid O(N^2) behavior when enlarging SPI tuple table in spi_prinabout 11 years ago
Replied (other)Error message with plpgsql CONTINUEabout 11 years ago
Started threadpgsql: Detect mismatched CONTINUE and EXIT statements at plpgsql compilabout 11 years ago