Filter:

Messages on September 17, 2018

Threads19 messages
8Started
0Replied in own
11Replied to othersin 6 threads
Patchesof which 1 carried a patch
1New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)First patchpgsql: Allow concurrent-safe open() and fopen() in frontend code for Wialmost 8 years ago
Started threadpgsql: Stamp 11beta4.almost 8 years ago
Replied (other)Too many BitmapAnds in the wildalmost 8 years ago
Replied (other)pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wialmost 8 years ago
Replied (other)Query is over 2x slower with jit=onalmost 8 years ago
Replied (other)Strange OSX make check-world failurealmost 8 years ago
Started threadpgsql: Fix parsetree representation of XMLTABLE(XMLNAMESPACES(DEFAULT .almost 8 years ago
Started threadpgsql: Fix parsetree representation of XMLTABLE(XMLNAMESPACES(DEFAULT .almost 8 years ago
Started threadpgsql: Fix parsetree representation of XMLTABLE(XMLNAMESPACES(DEFAULT .almost 8 years ago
Started threadpgsql: Remove dead code from pop_next_work_item().almost 8 years ago
Replied (other)Stored procedures and out parametersalmost 8 years ago
Replied (other)pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wialmost 8 years ago
Started threadpgsql: Fix pgbench lexer's "continuation" rule to cope with Windows newalmost 8 years ago
Started threadpgsql: Fix pgbench lexer's "continuation" rule to cope with Windows newalmost 8 years ago
Started threadpgsql: Fix pgbench lexer's "continuation" rule to cope with Windows newalmost 8 years ago
Replied (other)pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wialmost 8 years ago
Replied (other)Strange OSX make check-world failurealmost 8 years ago
Replied (other)pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wialmost 8 years ago
Replied (other)Clarification of nodeToString() use casesalmost 8 years ago