Filter:

Messages on August 16, 2019

Threads18 messages
7Started
2Replied in own
9Replied to othersin 8 threads
Patchesnone in this period
0New patchfirst in its thread
0Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)allocation limit for encoding conversionabout 7 years ago
Replied (other)UNION ALLabout 7 years ago
Replied (own)pgsql: Fix plpgsql to re-look-up composite type names at need.about 7 years ago
Replied (other)slow queries on system tablesabout 7 years ago
Replied (other)Bad Estimate for complex query with JOINS on subselects and OR in where conditionsabout 7 years ago
Replied (own)Unexpected "shared memory block is still in use"about 7 years ago
Replied (other)Bad Estimate for complex query with JOINS on subselects and OR in where conditionsabout 7 years ago
Replied (other)Wrong drop procedure exampleabout 7 years ago
Replied (other)length of string containing blanks is 0, || behaves differently than concat on string of blanksabout 7 years ago
Replied (other)Error XX000 After pg11 upgradeabout 7 years ago
Replied (other)Segmentation fault during update inside ExecBRUpdateTriggersabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago
Started threadpgsql: Prevent possible double-free when update trigger returns old tupabout 7 years ago