Filter:

Messages on July 07, 2022

Threads18 messages
1Started
0Replied in own
17Replied to othersin 13 threads
Patchesof which 1 carried a patch
0New patchfirst in its thread
1Follow-uprevision of an earlier one
ActivityThreadSent
Replied (other)index for inet columnabout 4 years ago
Replied (other)Postgres picks suboptimal index after building of an extended statisticsabout 4 years ago
Replied (other)Select Reference Page - Make Join Syntax More Prominentabout 4 years ago
Replied (other)Patch proposal: New hooks in the connection pathabout 4 years ago
Replied (other)Follow-up patchshould check interrupts in BuildRelationExtStatistics ?about 4 years ago
Replied (other)pg15b2: large objects lost on upgradeabout 4 years ago
Replied (other)pg_parameter_aclcheck() and trusted extensionsabout 4 years ago
Replied (other)BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slowerabout 4 years ago
Replied (other)pg_parameter_aclcheck() and trusted extensionsabout 4 years ago
Replied (other)archive modulesabout 4 years ago
Replied (other)Add a test for "cannot truncate foreign table"about 4 years ago
Replied (other)Use outerPlanState macro instead of referring to leffttreeabout 4 years ago
Started threadpgsql: Remove stray references to lefttree/righttree in the executor.about 4 years ago
Replied (other)About revoking large number of privileges; And the PUBLIC role.about 4 years ago
Replied (other)BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slowerabout 4 years ago
Replied (other)tuplesort Generation memory contexts don't play nicely with index buildsabout 4 years ago
Replied (other)BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slowerabout 4 years ago
Replied (other)BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slowerabout 4 years ago