Filter:

Messages on February 13, 2018

Threads19 messages
1Started
1Replied in own
17Replied to othersin 10 threads
Patchesof which 1 carried a patch
0New patchfirst in its thread
1Follow-uprevision of an earlier one
ActivityThreadSent
Started threadpgsql: Make plpgsql use its DTYPE_REC code paths for composite-type varover 8 years ago
Replied (other)I do not get the point of the information_schemaover 8 years ago
Replied (other)Add more information_schema columnsover 8 years ago
Replied (other)response time is very long in PG9.5.5 using psql or jdbcover 8 years ago
Replied (other)Client Connection redirection support for PostgreSQLover 8 years ago
Replied (other)response time is very long in PG9.5.5 using psql or jdbcover 8 years ago
Replied (other)[WIP PATCH] Index scan offset optimisation using visibility mapover 8 years ago
Replied (other)Multiple postmasters running from same directoryover 8 years ago
Replied (other)response time is very long in PG9.5.5 using psql or jdbcover 8 years ago
Replied (own)Converting plpgsql to use DTYPE_REC for named composite typesover 8 years ago
Replied (other)Multiple postmasters running from same directoryover 8 years ago
Replied (other)Follow-up patchBUG #15060: Row in table not found when using pg function in an expressionover 8 years ago
Replied (other)Multiple postmasters running from same directoryover 8 years ago
Replied (other)Using scalar function as set-returning: bug or feature?over 8 years ago
Replied (other)BUG #15060: Row in table not found when using pg function in an expressionover 8 years ago
Replied (other)rename sgml files?over 8 years ago
Replied (other)A space-efficient, user-friendly way to store categorical dataover 8 years ago
Replied (other)response time is very long in PG9.5.5 using psql or jdbcover 8 years ago
Replied (other)Using scalar function as set-returning: bug or feature?over 8 years ago