Filter:

Messages on January 04, 2019

Threads17 messages
2Started
2Replied in own
13Replied to othersin 9 threads
Patchesof which 1 carried a patch
0New patchfirst in its thread
1Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)reducing the footprint of ScanKeyword (was Re: Large writable variables)over 7 years ago
Replied (own)"SELECT ... FROM DUAL" is not quite as silly as it appearsover 7 years ago
Replied (other)reducing the footprint of ScanKeyword (was Re: Large writable variables)over 7 years ago
Replied (other)reducing the footprint of ScanKeyword (was Re: Large writable variables)over 7 years ago
Replied (other)Arrays of domain returned to client as non-builtin oid describing the array, not the base array type's oidover 7 years ago
Replied (own)Follow-up patch"SELECT ... FROM DUAL" is not quite as silly as it appearsover 7 years ago
Replied (other)SELECT do not return all rows depending on selected columnsover 7 years ago
Replied (other)reducing the footprint of ScanKeyword (was Re: Large writable variables)over 7 years ago
Replied (other)BUG #15555: Syntax errors when using the COMMENT command in plpgsql and a "comment" variableover 7 years ago
Started threadpgsql: Support plpgsql variable names that conflict with unreserved SQLover 7 years ago
Replied (other)Potentially undocumented behaviour change in Postgres 11 concerning OLD record in an after insert triggerover 7 years ago
Replied (other)Is temporary functions feature official/supported? Found some issues with it.over 7 years ago
Replied (other)commit fest app: Authorsover 7 years ago
Replied (other)Is temporary functions feature official/supported? Found some issues with it.over 7 years ago
Replied (other)Broken link in JSON Types documentationover 7 years ago
Replied (other)inconsistency and inefficiency in setup_conversion()over 7 years ago
Started threadpgsql: Move the built-in conversions into the initial catalog data.over 7 years ago